8Dionysus/aoa-contract-test
.agents/skills/aoa-contract-test/SKILL.md
Design or extend contract-oriented validation at module, service, or workflow boundaries. Use when two components interact across a meaningful interface, downstream assumptions matter, or a smoke path needs an explicit contract. Do not use for purely local changes or when the real need is invariant or property testing instead of boundary validation.
$ install --global
skillsauthnpx skillsauth add 8Dionysus/aoa-skills aoa-contract-testInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 10:33 PM198.2s2 files scanned
SKILL.md
- name:
- aoa-contract-test
- description:
- Design or extend contract-oriented validation at module, service, or workflow boundaries. Use when two components interact across a meaningful interface, downstream assumptions matter, or a smoke path needs an explicit contract. Do not use for purely local changes or when the real need is invariant or property testing instead of boundary validation.
- license:
- Apache-2.0
- compatibility:
- Designed for Codex or similar coding agents with repository file access and an interactive shell. Network access is optional and only needed when repository validation or referenced workflows require it.
- aoa_scope:
- core
- aoa_status:
- canonical
- aoa_invocation_mode:
- explicit-preferred
- aoa_source_skill_path:
- skills/aoa-contract-test/SKILL.md
- aoa_source_repo:
- 8Dionysus/aoa-skills
- aoa_technique_dependencies:
- AOA-T-0003,AOA-T-0015
- aoa_portable_profile:
- codex-facing-wave-3
aoa-contract-test
Intent
Strengthen boundary reliability by making expected inputs, outputs, and validation summaries explicit.
Trigger boundary
Use this skill when:
- two modules or services interact across a meaningful boundary
- a smoke path or interface needs a stable validation contract
- a change risks breaking downstream assumptions
Do not use this skill when:
- the change is entirely local and does not affect a meaningful boundary
- the boundary itself is still semantically unclear and naming is drifting; use
aoa-bounded-context-map - the main problem is expressing a broad invariant rather than a boundary contract; use
aoa-property-invariants - the main problem is auditing whether existing checks really cover a stable rule; use
aoa-invariant-coverage-audit - a broad system rewrite is needed before the boundary itself is stable
Inputs
- boundary under review
- expected inputs and outputs
- current verification surface
- known downstream dependencies
Outputs
- explicit contract assumptions
- tests or smoke summary changes
- verification notes
- downstream impact notes
Procedure
- identify the boundary and its consumers
- state the expected input/output behavior
- express the contract in tests, smoke summaries, or structured checks
- verify both the boundary behavior and the reporting shape
- report what became explicit and what remains weak
Contracts
- the contract should be visible to another human or agent
- verification should be tied to the boundary, not only to internals
- downstream assumptions should be named when relevant
Risks and anti-patterns
- vague contracts that do not actually constrain behavior
- treating a smoke summary as proof when it does not cover the real boundary
- changing interface behavior without downstream impact notes
Verification
- confirm the contract is visible and reviewable
- confirm validation is tied to the interface or boundary
- confirm downstream impact was considered when relevant
Technique traceability
Manifest-backed techniques:
- AOA-T-0003 from
8Dionysus/aoa-techniquesat5c6f0496edc3c2e74590baa35627c85fe58ef765using pathtechniques/evaluation/contract-first-smoke-summary/TECHNIQUE.mdand sections: Intent, When to use, Outputs, Contracts, Validation - AOA-T-0015 from
8Dionysus/aoa-techniquesat5c6f0496edc3c2e74590baa35627c85fe58ef765using pathtechniques/evaluation/contract-test-design/TECHNIQUE.mdand sections: Intent, Inputs, Core procedure, Risks
Adaptation points
Project overlays should add:
- local endpoints or module boundaries
- local smoke or test commands
- boundary-specific invariants
Related Skills
8Dionysus/aoa-knowledge-stewardship
development
VerifiedTrustedCommunity
Sanitize private technical material into a public-safe owner-bounded derivative, or resolve authority among authored, generated, runtime, and installed sources. Use for governed incidents, logs, configs, diagnostics, or conflicting source roles. Do not use for ordinary editing, memo/session work, direct publication, or durable-memory authority.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-session-recovery
tools
VerifiedTrustedCommunity
Diagnose a reviewed recurring session/workflow failure, or carry one bounded owner repair through checkpoint, rollback, and real health verification. Use for reviewed contamination, drift, repeated route/tool failure, or an established diagnosis ready for repair. Do not use on live evidence, for vague self-improvement, or to call a proposed or merely executed change verified.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-session-harvest
tools
VerifiedTrustedCommunity
Use only when a literal ref to a closed/reviewed session packet is supplied, to extract, classify, propose promotion or branching, or identify an automation opportunity. Missing, live, or unreviewed evidence must fail closed without inventing a ref. Natural closeout preservation belongs to aoa-memo-writeback. Do not use for generic summaries, progression, direct owner writes, scheduling, mutation, or telemetry authority.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-verification
testing
VerifiedTrustedCommunity
Turn one stable technical truth into bounded evidence through contract, coverage-audit, or property mode. Use to define a named consumer seam, audit what existing checks really constrain, or express a broad invariant after manual cases establish meaning. Compose with aoa-eval when an evaluation surface must first be found or applied. Do not use for undefined behavior, generic test plans, or green checks as whole-system proof.
4SKILL.mdUpdated Jul 16, 2026