Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/davidmatousek/agentic-oriented-development-kit/aod.specgit clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00013 | $0.03885 |
| Opus 5 | $0.00006 | $0.01943 |
| Sonnet 5 | $0.00003 | $0.00777 |
| Haiku 4.5 | $0.00001 | $0.00388 |
Grade A, and why
aod.spec scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to aod.spec — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Consider user input before proceeding (if not empty).
Step 0: Parse --autonomous
- If
$ARGUMENTScontains--autonomous:- Set
autonomous = true - Strip
--autonomousfrom$ARGUMENTS(trim extra whitespace)
- Set
- Default:
autonomous = false
Step 0y: Parse --revision
- If
$ARGUMENTScontains--revision:- Set
revision_mode = true - Strip
--revisionfrom$ARGUMENTS(trim extra whitespace) - Read
.aod/revision-context.mdfor reviewer feedback (contains reviewer name, attempt number, artifact path, and full feedback text) - Store feedback as
revision_feedback - Clear governance cache explicitly: Call
aod_state_clear_governance_cache "spec"so the upcoming PM review is treated as fresh regardless of mtime-staleness backstop. (Belt-and-suspenders: do NOT rely on the mtime backstop alone.)
- Set
- Default:
revision_mode = false
Overview
Creates a feature specification with automatic PM sign-off (Constitution Principle VIII: Product-Spec Alignment). Generates spec.md inline with research grounding and governance review.
Flow: Validate PRD → Research → Generate spec (inline) → PM review → Handle blockers → Inject frontmatter
Step 1: Validate Prerequisites
- Get branch:
git branch --show-current→ must matchNNN-*pattern - Find PRD:
docs/product/02_PRD/{NNN}-*.md→ must exist - Parse frontmatter: Verify all Triad sign-offs are APPROVED (or APPROVED_WITH_CONCERNS/BLOCKED_OVERRIDDEN)
- If validation fails: Show error with required workflow order and exit
- GitHub Lifecycle Update (early): Move the feature's GitHub Issue to
stage:planat the start of specification work. The issue number is the NNN prefix extracted from the branch in step 1 (e.g., branch086-my-feature→ issue86). Run:
Then regenerate BACKLOG.md:bash -c 'source .aod/scripts/bash/github-lifecycle.sh && aod_gh_update_stage NNN plan'
Ifbash .aod/scripts/bash/backlog-regenerate.shghis unavailable or the issue does not exist, skip silently (graceful degradation).
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 374 lines · 13 tokens per session scan A 6a15696776ea
aod.spec is a command published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 3,885 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aod.spec, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.