Borrowing it
Nothing to install: this file belongs to davidmatousek/tachi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davidmatousek/tachi/main/.claude/skills/~aod-run/SKILL.mdgit 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/skills/davidmatousek/tachi/aod-run)<a href="https://agentmods.dev/skills/davidmatousek/tachi/aod-run"><img src="https://agentmods.dev/badge/skills/davidmatousek/tachi/aod-run/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/skills/davidmatousek/tachi/aod-run"><img src="https://agentmods.dev/badge/skills/davidmatousek/tachi/aod-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 367 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00072 | $0.10107 |
| Opus 5.5 | $0.00029 | $0.04043 |
| Sonnet 5.5 | $0.00014 | $0.02021 |
| Haiku 4.5 | $0.00007 | $0.01011 |
Grade A, and why
~aod-run 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ~aod-run — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 694 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Lifecycle Orchestrator Skill
Purpose
Single-command lifecycle orchestrator that chains all 6 AOD stages autonomously, pausing at governance gates for Triad sign-offs and persisting state to disk for session resilience. After Deliver completes, Document runs automatically as Stage 6.
Entry Points:
- Raw idea:
"description"→ start at Discover - Issue number:
#NNNorNNN→ resume from issue's current stage - Resume:
--resume→ continue from last state checkpoint - Status:
--status/--status #NNN→ read-only display
State File: .aod/run-state.json (atomic write-then-rename via run-state.sh)
Navigation
| Section | Purpose | Location |
|---|---|---|
| Step 1: Route by Mode | Entry point routing | This file |
| Step 2: Core State Machine Loop | Central orchestration logic | This file |
| Plan Substage Tracking | Spec → project_plan → tasks | This file |
| Stage Skill Mapping | Stage-to-skill invocation table | This file |
| Post-Stage Context Extraction | Artifact discovery after each stage | This file |
| Stage Map Display | Visual progress indicators | This file |
| Transition Messages | Stage transition headers | This file |
| GitHub Integration | Label updates after stage completion | This file |
| Error Logging | Error/event capture in state file | This file |
| Governance Gate Detection | Reading approval/rejection from frontmatter | references/governance.md |
| Governance Tier | Light/Standard/Full gate rules | references/governance.md |
| Rejection / Retry / Circuit Breaker / Blocked | Governance result handling | references/governance.md |
| New Idea / Issue / Resume / Status Entry | Mode-specific handlers | references/entry-modes.md |
| Dry-Run Entry | --dry-run preview handler (read-only) |
references/dry-run.md |
| Corrupted State / Lifecycle Complete | Error and completion handlers | references/error-recovery.md |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 694 lines · 72 tokens per session scan A bd890355e021
~aod-run is a skill published in the GitHub repository davidmatousek/tachi (94 stars, last pushed 4d ago), licensed Apache-2.0. It adds 72 tokens to every session and 10,107 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
usap-program-manager
Security program manager and passive lifecycle orchestrator (cs-security-program-manager). Use for security roadmap planning, program health scanning, debt tracking, facilitated reviews, or when the user says "security roadmap", "program planning", "security debt", "proactive scan", or "program review".
findings-tracker
../../../governance/findings-tracker/SKILL.md.
incident-commander
../../../response/incident-commander/SKILL.md.
contact-template
Contact / communications plan generator — primary operator, escalation chain, abort signal recipient, external SOC endpoint, blackout windows.
Governance
Organizational governance for PAI agent infrastructure — budget controls, approval gates, goal ancestry, org chart visualization, standing orders, config portability, workspaces, and task locking. USE WHEN user mentions budget, spending, approval, governance, org chart, goals, standing orders, heartbeat, export…
company-values
Help define company values and culture for a minimalist business. Use when someone is setting up their company culture, preparing to hire, or wanting to codify what their company stands for.