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-status/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-status)<a href="https://agentmods.dev/skills/davidmatousek/tachi/aod-status"><img src="https://agentmods.dev/badge/skills/davidmatousek/tachi/aod-status.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.00856 |
| Opus 5 | $0.00028 | $0.00428 |
| Sonnet 5 | $0.00011 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00086 |
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 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-status — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AOD Status Skill
Purpose
Utility skill for the AOD Lifecycle. Provides an on-demand snapshot of the project backlog by regenerating BACKLOG.md from GitHub Issues and displaying a summary of items per lifecycle stage.
No governance gates — this is a read-only utility command.
How It Works
Step 1: Reconcile Board
Run board reconciliation to fix any label↔board column drift before generating the snapshot:
source .aod/scripts/bash/github-lifecycle.sh && aod_gh_reconcile_board
This compares each open issue's stage:* label to its board column and fixes mismatches. If the board or gh is unavailable, it skips silently.
Step 2: Regenerate BACKLOG.md
Run the backlog regeneration script with JSON output mode:
bash .aod/scripts/bash/backlog-regenerate.sh --json
Parse the JSON output to extract:
file: path to regenerated BACKLOG.mdtotal: total number of GitHub Issuesstages: object with counts per stage (discover,define,plan,build,deliver,untracked)
If the script fails or gh is unavailable: Display a warning and attempt to read the existing BACKLOG.md file instead. If no BACKLOG.md exists either, report that no backlog data is available.
Step 3: Display Stage Summary
Present a formatted summary table:
AOD LIFECYCLE STATUS
| Stage | Count |
|----------|-------|
| Discover | {n} |
| Define | {n} |
| Plan | {n} |
| Build | {n} |
| Deliver | {n} |
| Untracked| {n} |
|----------|-------|
| Total | {n} |
BACKLOG.md regenerated at {file_path}.
Step 4: Show Active Feature Context (Optional)
If the current git branch matches a feature pattern (NNN-*), display the active feature context:
- Get branch:
git branch --show-current - Extract NNN prefix
- Check for
specs/{NNN}-*/directory - If found, read spec.md/plan.md/tasks.md frontmatter to show approval status:
Active Feature: {NNN}-{name}
spec.md: {PM approved / not approved / missing}
plan.md: {dual approved / not approved / missing}
tasks.md: {triple approved / not approved / missing}
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 · 102 lines · 57 tokens per session scan A 225968d9252b
~aod-status is a skill published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 25d ago), licensed Apache-2.0. It adds 57 tokens to every session and 856 once invoked, about $0.0003 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-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.
usap-red-teamer
Offensive security coordinator (cs-red-teamer). Use for red team campaign planning, attack path analysis, engagement scoping, adversary simulation, or when the user says "red team", "pentest", "attack simulation", "run an engagement", or "offensive security". Requires explicit authorization scope.
usap-alex
Universal USAP security advisor (cs-security-analyst). Use for any security question, alert triage (AT), threat hunt (TH), compromise assessment (CA), or when the user says "activate Alex", "start USAP", or asks what USAP can do.