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.
git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/davidmatousek/agentic-oriented-development-kit/aod.deliver)<a href="https://agentmods.dev/commands/davidmatousek/agentic-oriented-development-kit/aod.deliver"><img src="https://agentmods.dev/badge/commands/davidmatousek/agentic-oriented-development-kit/aod.deliver/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/davidmatousek/agentic-oriented-development-kit/aod.deliver"><img src="https://agentmods.dev/badge/commands/davidmatousek/agentic-oriented-development-kit/aod.deliver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00016 | $0.04176 |
| Opus 5.5 | $0.00006 | $0.01670 |
| Sonnet 5.5 | $0.00003 | $0.00835 |
| Haiku 4.5 | $0.00002 | $0.00418 |
Grade A, and why
aod.deliver 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 1mo 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.deliver — 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Close a completed feature by validating readiness, launching parallel documentation agents, performing cleanup, and committing all changes.
Input
$ARGUMENTS
Feature number (e.g., 007 or 007-phase-brain-rag). If omitted, detect from recent PRs or prompt.
Step 0: Parse Flags
- If
$ARGUMENTScontains--autonomous:- Set
autonomous = true - Strip
--autonomousfrom$ARGUMENTS(trim extra whitespace) - Default:
autonomous = false
- Set
- If
$ARGUMENTScontains--require-tests:- Set
require_tests = true - Strip
--require-testsfrom$ARGUMENTS(trim extra whitespace) - Default:
require_tests = false
- Set
Step 1: Validate Closure Readiness
Run these checks (in parallel where possible):
| Check | Command | Pass Condition |
|---|---|---|
| Feature exists | ls specs/*{NUMBER}* |
Directory found |
| PR merged | git branch -a | grep {NUMBER} |
Branch NOT found (deleted after merge) |
| Tasks complete | grep "^\- \[ \]" specs/{FEATURE}/tasks.md |
Zero incomplete tasks |
Branch & PR Handling (Automatic)
Per git workflow rules, feature branches require PRs — handle this automatically without prompting:
- If uncommitted changes exist: Stage and commit all changes with a conventional commit message
- If branch is not pushed: Push to remote with
-uflag - If no PR exists: Create one via
gh pr createwith a summary of all branch commits - If PR exists but not merged: Merge it via
gh pr merge --squash --delete-branch - If PR already merged and branch deleted: Proceed directly
Only prompt the user if an automated step fails (e.g., merge conflicts, CI failure).
Other Validation Failures
- Tasks incomplete:
- If
autonomous == true: Auto-select"Proceed anyway". Display:"Auto-selected: Proceed past incomplete tasks (autonomous mode)" - Else: (A) Mark complete, (B) Abort, (C) Proceed anyway
- If
Step 2: Gather Feature Context
Read specs/{FEATURE}/tasks.md and specs/{FEATURE}/spec.md to extract:
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.
- 1mo ago First seen · 307 lines · 16 tokens per session scan A 98a8224dca3d
aod.deliver is a command published in the GitHub repository davidmatousek/agentic-oriented-development-kit (24 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 4,176 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to aod.deliver, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.