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.updategit 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.update)<a href="https://agentmods.dev/commands/davidmatousek/tachi/aod.update"><img src="https://agentmods.dev/badge/commands/davidmatousek/tachi/aod.update.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 | $0.00008 | $0.01096 |
| Opus 5 | $0.00004 | $0.00548 |
| Sonnet 5 | $0.00002 | $0.00219 |
| Haiku 4.5 | $0.00001 | $0.00110 |
Grade A, and why
aod.update 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 4d 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.update — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Run the downstream template update pipeline: fetch the latest AOD-kit template from the pinned upstream, compute a categorized diff, preview what will change, and apply the approved set of changes atomically.
Update direction is always: upstream → downstream
When to Use
- Periodic check for upstream template improvements (new commands, skills, docs).
- After a notable upstream release — confirm whether anything safe-to-adopt has landed.
- Before running
/aod.deliveron a large feature if you want the latest tooling.
When NOT to Use
- During an in-flight feature branch if you're worried about merge noise — do it between features.
- On a dirty working tree with uncommitted changes you care about — commit or stash first.
Input
$ARGUMENTS
Common flag combinations:
- (no flags) — interactive TTY: preview, then confirm-to-apply.
--dry-run— preview only; never writes.--yes— skip the confirmation prompt; still applies.--edge— fetch upstreammainHEAD instead of latest tag (not recommended for production use).--force-retag— proceed even if the pinned tag has been retagged upstream (supply-chain override; logs a warning).--upstream-url=<url>— override the recorded upstream URL (must behttps://).
Step 1: Verify Bootstrap State
Check that the adopter project has been bootstrapped:
test -f .aod/aod-kit-version || { echo "Missing .aod/aod-kit-version — run scripts/init.sh first." ; exit 3; }
test -f .aod/personalization.env || { echo "Missing .aod/personalization.env — run scripts/init.sh first." ; exit 3; }
If either file is missing: Display setup instructions pointing at scripts/init.sh and stop execution.
Step 2: Run the Update Pipeline
Invoke the CLI with the provided arguments:
scripts/update.sh $ARGUMENTS
Display the full output to the user so they can see the preview, confirmation prompt (if interactive), and per-operation apply log.
Step 3: Interpret Exit Codes
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.
- 4d ago First seen · 113 lines · 8 tokens per session scan A bbd6a3263aa8
aod.update is a command published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 22d ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,096 once invoked, about $0.0000 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.
README
Claude Code slash commands for the Unified Security Agent Platform (USAP). These commands let you load any USAP skill as a live LLM persona and run structured compliance tests — all inside a Claude Code session.
challenge
Run cs-security-analyst (AT workflow) against the Perfect Storm 8-vector crisis scenario and produce a 12-check mock comparison scorecard.
compare
Before/after comparison of zero-day-response SKILL.md v1 (broken) vs v2 (fixed) against the FortiGate zero-day scenario. Outputs a scored table.
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.