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.definegit 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.00023 | $0.04487 |
| Opus 5 | $0.00012 | $0.02243 |
| Sonnet 5 | $0.00005 | $0.00897 |
| Haiku 4.5 | $0.00002 | $0.00449 |
Grade A, and why
aod.define 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.define — 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 — 359 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
- Set
- Default:
revision_mode = false
Overview
Wraps ~aod-define skill with automatic Triad triple sign-off.
Flow: Check vision docs → Validate topic → Classify type → Draft PRD → Reviews → Handle blockers → Inject frontmatter → Update INDEX
Step 0: Check Product Vision (Optional)
Check if product vision documents exist:
docs/product/01_Product_Vision/product-vision.md
If vision docs DON'T exist (first PRD for this project):
-
If
autonomous == true: Auto-select"Skip". Display:"Auto-selected: Skip vision workshop (autonomous mode)". Proceed directly to Step 1. -
Use AskUserQuestion:
- Quick Vision: Answer 3 questions to create vision docs (recommended for new projects)
- Skip: Proceed directly to PRD creation (for experienced users)
-
If "Quick Vision" selected, run mini-workshop:
🎯 Quick Product Vision (3 questions)
Q1: What problem are you solving and for whom?
(1-2 sentences: the pain point and who experiences it)
Q2: What's your solution in one sentence?
(How your product solves the problem differently)
Q3: What are the 2-3 core features?
(Brief list of key capabilities)
- Generate
docs/product/01_Product_Vision/product-vision.mdwith their answers:- Mission statement (derived from Q1+Q2)
- Problem statement (Q1)
- Solution overview (Q2)
- Core capabilities table (Q3)
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 · 359 lines · 23 tokens per session scan A 080baa8aad5c
aod.define is a command published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 4,487 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.define, 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.