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.buildgit 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.11031 |
| Opus 5 | $0.00006 | $0.05515 |
| Sonnet 5 | $0.00003 | $0.02206 |
| Haiku 4.5 | $0.00001 | $0.01103 |
Grade A, and why
aod.build 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.build — 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 — 757 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 Arguments
Parse optional flags from $ARGUMENTS. Flags can appear anywhere in the arguments string.
Step 0a: Parse --no-security
-
If
$ARGUMENTScontains--no-security:- Set
skip_security = true - Strip
--no-securityfrom$ARGUMENTS(trim extra whitespace) - Continue to Step 0b with remaining arguments
- Set
-
If
$ARGUMENTSdoes NOT contain--no-security:- Set
skip_security = false - Continue to Step 0b with
$ARGUMENTSunchanged
- Set
Step 0b: Parse --orchestrated
- If
$ARGUMENTScontains--orchestrated:- Set
orchestrated = true - Strip
--orchestratedfrom$ARGUMENTS(trim extra whitespace)
- Set
- If
$ARGUMENTSdoes NOT contain--orchestrated:- Set
orchestrated = false
- Set
Step 0c: Parse --autonomous
- If
$ARGUMENTScontains--autonomous:- Set
autonomous = true - Strip
--autonomousfrom$ARGUMENTS(trim extra whitespace)
- Set
- If
$ARGUMENTSdoes NOT contain--autonomous:- Set
autonomous = false
- Set
Step 0d: Parse --no-design-check
-
If
$ARGUMENTScontains--no-design-check:- Set
skip_design_check = true - Strip
--no-design-checkfrom$ARGUMENTS(trim extra whitespace) - Continue to Step 0e with remaining arguments
- Set
-
If
$ARGUMENTSdoes NOT contain--no-design-check:- Set
skip_design_check = false - Continue to Step 0e with
$ARGUMENTSunchanged
- Set
Step 0e: Parse --no-tests
-
If
$ARGUMENTScontains--no-tests:- Set
skip_tests = true - Strip
--no-testsfrom$ARGUMENTS(trim extra whitespace) - Continue to Step 0f with remaining arguments
- Set
-
If
$ARGUMENTSdoes NOT contain--no-tests:- Set
skip_tests = false - Continue to Step 0f with
$ARGUMENTSunchanged
- Set
Step 0f: Parse --require-tests
- If
$ARGUMENTScontains--require-tests:- Set
require_tests = true - Strip
--require-testsfrom$ARGUMENTS(trim extra whitespace) - Conflict check: If both
skip_testsandrequire_testsare true,skip_teststakes precedence (test execution is skipped entirely). Display:"Warning: --no-tests and --require-tests both present. --no-tests takes precedence (tests skipped)." - Continue to Step 0g with remaining arguments
- Set
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 · 757 lines · 13 tokens per session scan A 71a43c1ab823
aod.build 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 11,031 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.build, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.