tachi: Skill for Claude Code

.claude/skills/~aod-status/SKILL.md

~aod-status is a skill for Claude Code from davidmatousek/tachi. It costs 57 tokens per session (856 once invoked), scanned A, original, Apache-2.0.

A read-only backlog status tool that rebuilds a project backlog from GitHub Issues and summarises work by lifecycle stage. GitHub Issues are GitHub's built-in records for tracking tasks and changes.

In plain words
What is it for?
It is for checking project progress, counting items in each workflow stage, and regenerating a BACKLOG.md file.
Why use it?
It gives developers a current view of what is in discovery, definition, planning, building, delivery, or another stage, while correcting mismatches between issue labels and board columns.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is davidmatousek/tachi's own configuration. It tells Claude Code how to work on tachi itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tachi configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash .aod/scripts/bash/backlog-regenerate.sh --json.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/davidmatousek/tachi/main/.claude/skills/~aod-status/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/davidmatousek/tachi

Made for: Claude Code.

Wrote 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.

agentmods badge for ~aod-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/davidmatousek/tachi/aod-status.svg)](https://agentmods.dev/skills/davidmatousek/tachi/aod-status)
Your own site
<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>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 856 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 225968d9252b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/~aod-status/SKILL.md · 102 lines

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.md
  • total: total number of GitHub Issues
  • stages: 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:

  1. Get branch: git branch --show-current
  2. Extract NNN prefix
  3. Check for specs/{NNN}-*/ directory
  4. 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}

Read the full file on GitHub · 102 lines

Changes

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.

  1. 4d ago First seen · 102 lines · 57 tokens per session scan A 225968d9252b

Subscribe to this mod's changes

~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.