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/tachi/aod.statusgit clone --depth 1 https://github.com/davidmatousek/tachiWrote 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/tachi/aod.status)<a href="https://agentmods.dev/commands/davidmatousek/tachi/aod.status"><img src="https://agentmods.dev/badge/commands/davidmatousek/tachi/aod.status.svg" alt="Measured on agentmods" 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.00013 | $0.00213 |
| Opus 5 | $0.00006 | $0.00106 |
| Sonnet 5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
aod.status 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- aod.status — 100% identical, 0 lines differ
What it actually says
Overview
On-demand backlog snapshot and lifecycle stage summary. Regenerates BACKLOG.md from GitHub Issues and displays item counts per lifecycle stage.
No governance gates — this is a read-only utility command.
Execute
Follow the workflow defined in the ~aod-status skill (.claude/skills/~aod-status/SKILL.md):
- Run
.aod/scripts/bash/backlog-regenerate.sh --jsonto regenerate BACKLOG.md - Parse output to count items per stage (Discover, Define, Plan, Build, Deliver, Untracked)
- Display formatted stage summary table with totals
- If on a feature branch, show active feature artifact approval status
Quality Checklist
- BACKLOG.md regenerated (or fallback used if gh unavailable)
- Stage counts displayed in table format
- Total count matches sum of stages
- Active feature context shown if on feature branch
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.
- 6d ago First seen · 26 lines · 13 tokens per session scan A 822f26100419
aod.status is a command published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 23d ago), licensed Apache-2.0. It adds 13 tokens to every session and 213 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
fortigate
Run cs-security-analyst (AT + CA workflows) against the Fintech FortiGate zero-day scenario and produce a 7-task scorecard.
challenge
Run cs-security-analyst (AT workflow) against the Perfect Storm 8-vector crisis scenario and produce a 12-check mock comparison scorecard.
test
Run a USAP skill against the FortiGate zero-day test scenario and produce a 6-problem compliance scorecard.
run
Load a USAP skill SKILL.md and activate it as your operating persona. Argument: skill slug.
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.