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.documentgit 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.00021 | $0.03413 |
| Opus 5 | $0.00010 | $0.01707 |
| Sonnet 5 | $0.00004 | $0.00683 |
| Haiku 4.5 | $0.00002 | $0.00341 |
Grade A, and why
aod.document 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.document — 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 — 277 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 0a: Parse --autonomous
- If
$ARGUMENTScontains--autonomous:- Set
autonomous = true - Strip
--autonomousfrom$ARGUMENTS(trim extra whitespace)
- Set
- If
$ARGUMENTSdoes NOT contain--autonomous:- Set
autonomous = false
- Set
Overview
Post-delivery quality review for the completed feature. This is Stage 6 of the AOD lifecycle — the one stage designed for human judgment. Each step presents findings interactively and commits only what the human approves.
Flow: Validate context → Branch → Code simplification → Docs-lint → CHANGELOG → API sync → KB review → PR squash-merge → Report
IMPORTANT: Execute ALL steps 0–7 sequentially. Do not stop or wait for further instructions between steps. After completing each step (including user interaction), immediately proceed to the next step until the Step 7 Report is displayed.
Step 0: Validate Context
- Get branch:
git branch --show-current - Determine feature number NNN:
- If on a
NNN-*branch: extract NNN from branch name - If on
main: extract NNN from user input$ARGUMENTS, or detect from most recentfeat(NNN)ordocs(NNN)commit on main - If NNN cannot be determined: prompt the user for the feature number
- If on a
- Find tasks:
specs/{NNN}-*/tasks.md→ verify all tasks marked[X](build complete) - If tasks incomplete: warn "Build may not be complete — {incomplete_count} tasks remain" and ask whether to proceed
- Display: "Document stage for Feature {NNN}"
Step 0b: Create Document Branch
- If not already on main:
git checkout main && git pull origin main - Create branch:
git checkout -b {NNN}-document-stage - Display: "Working on branch {NNN}-document-stage"
Step 1: Code Simplification
Detect changed code files and run /simplify for human review.
1a: Detect Changed Files
- Run:
git diff --name-only main...HEAD - Filter to code extensions:
.py,.js,.ts,.jsx,.tsx,.sh,.go,.rs,.java,.rb,.swift,.kt - Exclude:
*.lock,*.min.js,*.min.css,*.map,*.generated.*,vendor/,dist/,build/,node_modules/,.aod/,docs/ - Store as
changed_fileslist andfile_count - If
file_countis 0: display "No code files changed — skipping simplification", proceed to Step 2 - If
file_count> 50: warn "Large diff ({file_count} files). Simplify may take several minutes." and ask whether to continue or skip
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 · 277 lines · 21 tokens per session scan A 3b1ce7e498be
aod.document is a command published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 3,413 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.document, 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.