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/aaronsb/claude-code-config/governancegit clone --depth 1 https://github.com/aaronsb/claude-code-configWhat 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.00014 | $0.00222 |
| Opus 5 | $0.00007 | $0.00111 |
| Sonnet 5 | $0.00003 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
governance 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.
What it actually says
Run ways governance with the user's arguments (if any) and display the output.
This is the governance operator. Common invocations:
ways governance report— coverage report (default)ways governance trace softwaredev/commits— end-to-end trace for a wayways governance control NIST— which ways implement controls matching "NIST"ways governance policy code-lifecycle— which ways derive from a policyways governance gaps— list ways without provenanceways governance stale— ways with stale verified datesways governance active— cross-reference provenance with way firing statsways governance matrix— flat traceability matrix (way | control | justification)ways governance lint— validate provenance integrity- Add
--jsonto any mode for machine-readable output
If the user provides arguments after /governance, pass them through. If no arguments, run the default coverage report.
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 · 21 lines · 14 tokens per session scan A 657efe8bd772
governance is a command published in the GitHub repository aaronsb/claude-code-config (18 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 222 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
sicario.controls
Generate or update docs/compliance/control-applicability.md.
audit
You are in AUDIT MODE. Perform a constitutional compliance scan.
sicario.evidence
Generate evidence artifacts.
icn-audit
Audit a code path, crate, or flow for trust boundary violations, regulatory terminology, and economic invariant risks.
rr
The user invoked the /riskreview facade command from the risk-review-pipeline pack.
dos
Generate Digital Outcomes and Specialists (DOS) procurement documentation for UK Digital Marketplace.