Borrowing it
Nothing to install: this file belongs to tacoda/keystone. 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/tacoda/keystone/main/.claude/commands/keystone-audit.mdgit clone --depth 1 https://github.com/tacoda/keystoneWrote 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/tacoda/keystone/keystone-audit)<a href="https://agentmods.dev/commands/tacoda/keystone/keystone-audit"><img src="https://agentmods.dev/badge/commands/tacoda/keystone/keystone-audit.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.1 | $0.00007 | $0.00777 |
| Opus 5 | $0.00003 | $0.00388 |
| Sonnet 5 | $0.00001 | $0.00155 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
keystone-audit 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.
This is a copy
98% identical to audit — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit
Full dual-flywheel audit. Learning (capture from review) and Pruning (remove dead rules). Periodic. Read .charter/README.md (flywheels section) and .charter/learning/README.md.
Learning flywheel
- Walk
.charter/learning/inbox/and flag candidates that should be promoted. - Run review sensors on recent commits — surface patterns that should become guides.
- Capture findings as new inbox entries (see
learn.md).
Pruning flywheel
The Pruning flywheel reads the charter-debt sensor and proposes the diff to .charter/corpus/state/charter-debt.md. Categories the sensor surfaces:
- Stale rules — guides in
.charter/guides/that no diff has touched in N months. - Dead idioms — idiom dirs whose stack is no longer in
CODEBASE_STATE.md. - Placeholders — bootstrap
<...>markers left unfilled. - Failing sensors — sensors recorded as available that error on invocation.
- Empty shells — scaffolded dirs with no real content.
- Uncited policies — installed policies whose guides were never referenced.
- Unresolved gaps —
.charter/adapters/<agent>/<topic>.mdTODO placeholders. - Drifted state — stack-drift findings +
CODEBASE_STATE.mdstale-last_reconciled. - Strict-cascade violations — run
keystone policy verify; any strict-violation output is a hard debt entry. A project file at.charter/<kind>/<name>.mdis overriding astrictitem from a team or org policy. Remove the shadowing file or escalate to the policy owner. - Required-item gaps — same
keystone policy verifyrun. Required items with no definition anywhere in the cascade are advisory debt: the project is expected to define them at.charter/<kind>/<name>.md. Pruning surfaces them; the project decides which to fill in.
Then update the empirical state files:
- Risk fingerprint — read
.charter/sensors/risk-fingerprint.mdand update.charter/corpus/state/risk-fingerprints.md. - Traffic topology — read
.charter/sensors/traffic-topology.mdand update.charter/corpus/state/traffic-topology.md.
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 · 45 lines · 7 tokens per session scan A aa4419398eb3
keystone-audit is a command published in the GitHub repository tacoda/keystone (44 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 777 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to audit, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.