8Dionysus/aoa-property-invariants
.agents/skills/aoa-property-invariants/SKILL.md
Express stable system or domain truths as invariant-oriented tests or checks rather than only fixed examples. Use when correctness depends on behavior that should hold across many inputs or states, such as monotonicity, idempotency, conservation, or structural rules. Do not use when no meaningful invariant is known yet or when the real task is auditing existing coverage instead of writing the properties.
$ install --global
skillsauthnpx skillsauth add 8Dionysus/aoa-skills aoa-property-invariantsInstall 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 25, 2026, 9:32 PM3.6s1 file scanned
SKILL.md
- name:
- aoa-property-invariants
- description:
- Express stable system or domain truths as invariant-oriented tests or checks rather than only fixed examples. Use when correctness depends on behavior that should hold across many inputs or states, such as monotonicity, idempotency, conservation, or structural rules. Do not use when no meaningful invariant is known yet or when the real task is auditing existing coverage instead of writing the properties.
- 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-property-invariants/SKILL.md
- aoa_source_repo:
- 8Dionysus/aoa-skills
- aoa_technique_dependencies:
- AOA-T-0017,AOA-T-0007
- aoa_portable_profile:
- codex-facing-wave-3
aoa-property-invariants
Intent
Use invariant-oriented thinking to test broad behavior through properties rather than only through a short list of fixed examples.
Trigger boundary
Use this skill when:
- a rule should hold across many inputs or states
- examples alone feel too narrow
- the system has conservation, monotonicity, idempotency, or structural invariants
- safety or correctness depends on broad input coverage
Do not use this skill when:
- the behavior is mostly about presentation details or narrow snapshots
- the main problem is checking whether existing checks really cover the invariant; use
aoa-invariant-coverage-auditfirst - the main problem is a boundary contract rather than a stable invariant; use
aoa-contract-test - no meaningful invariant is yet understood
Inputs
- target rule or domain truth
- current examples or tests
- input space or generators
- known edge cases
Outputs
- explicit invariants
- property-oriented tests or checks
- notes on generator assumptions
- verification summary
Procedure
- identify what must remain true across many cases
- separate strong invariants from weak hopes or vague expectations
- express those invariants as property-oriented tests or repeated checks
- keep the generators or inputs bounded and reviewable
- run the checks and report what properties now constrain behavior
Contracts
- each property should express a real invariant, not a wish
- the test should broaden coverage beyond a small handpicked set
- generator assumptions should remain understandable
Risks and anti-patterns
- writing weak properties that prove almost nothing
- confusing random data with meaningful coverage
- letting overly broad generators or harness complexity hide the protected domain truth
- using polished invariant language while the actual stable truth remains underspecified
- using property checks where a small set of concrete examples would be clearer
- using invariant language to avoid naming the actual rule or boundary that matters
Verification
- confirm the property expresses a meaningful invariant
- confirm the invariant broadens coverage beyond fixed examples
- confirm the report names which stable truth was violated or protected, not only that generated inputs failed
- confirm the result is understandable to another human or agent
Technique traceability
Manifest-backed techniques:
- AOA-T-0017 from
8Dionysus/aoa-techniquesat5c6f0496edc3c2e74590baa35627c85fe58ef765using pathtechniques/evaluation/property-invariants/TECHNIQUE.mdand sections: Intent, When to use, Inputs, Outputs, Core procedure, Contracts, Risks, Validation - AOA-T-0007 from
8Dionysus/aoa-techniquesat5c6f0496edc3c2e74590baa35627c85fe58ef765using pathtechniques/evaluation/signal-first-gate-promotion/TECHNIQUE.mdand sections: summary, Validation
Adaptation points
Project overlays should add:
- local generator tools
- domain-specific invariants
- rules for when property-based checks are mandatory, optional, or out of scope
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