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.definegit 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.define)<a href="https://agentmods.dev/commands/davidmatousek/tachi/aod.define"><img src="https://agentmods.dev/badge/commands/davidmatousek/tachi/aod.define.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.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 3d 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.define — 100% identical, 0 lines differ
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.
- 3d ago First seen · 359 lines · 23 tokens per session scan A 080baa8aad5c
aod.define is a command published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 21d ago), licensed Apache-2.0. 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. 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.