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 skills add aaronsb/claude-code-config --skill governance-citegit clone --depth 1 https://github.com/aaronsb/claude-code-configWrote 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/aaronsb/claude-code-config/governance-cite)<a href="https://agentmods.dev/skills/aaronsb/claude-code-config/governance-cite"><img src="https://agentmods.dev/badge/skills/aaronsb/claude-code-config/governance-cite.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.00078 | $0.00855 |
| Opus 5 | $0.00039 | $0.00428 |
| Sonnet 5 | $0.00016 | $0.00171 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
governance-cite 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Governance Citation
You have access to a governance traceability system that maps agent guidance (ways) to real regulatory controls with specific justification evidence. Use this to ground your recommendations in actual standards rather than general knowledge.
When to Cite
Cite governance controls when:
- Recommending a practice that has a governing control (commits, security, quality, documentation)
- Answering "why do we do it this way?"
- Reviewing code and flagging issues covered by a control
- A user questions whether a practice matters
Don't force citations into every response. Use them when they add authority or clarity.
How to Look Up Controls
By topic
ways governance control PATTERN
Examples:
control NIST— all NIST controlscontrol OWASP— injection preventioncontrol ISO— all ISO standardscontrol SOC— SOC 2 controlscontrol CIS— CIS controlscontrol change— change management controls
By way (full trace)
ways governance trace softwaredev/commits
ways governance trace softwaredev/security
ways governance trace softwaredev/quality
ways governance trace meta/knowledge
Machine-readable (for structured extraction)
ways governance control PATTERN --json
ways governance trace WAY --json
Citation Format
When citing a control, reference the control ID and quote the specific justification:
Inline (for brief references):
We use conventional commit format — per NIST CM-3, this "creates structured change records with type classification" for auditable configuration change control.
Detailed (for explanations or reviews):
This aligns with NIST SP 800-53 CM-3 (Configuration Change Control), which our commit guidance implements through:
- Conventional commit types (feat/fix/refactor) classify changes by nature
- Atomic single-concern commits make each change independently reviewable
- Commit message body captures rationale, satisfying change documentation requirements
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.
- 7d ago First seen · 88 lines · 78 tokens per session scan A 8d03ffc9ae94
governance-cite is a skill published in the GitHub repository aaronsb/claude-code-config (18 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 855 once invoked, about $0.0004 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 skills, from other repositories
ai-crew-sync
Conventions for coordinating with teammates' AI coding agents over the team bus MCP server. Use whenever starting work in a shared repo, picking up or handing off tasks, announcing deploys/migrations, asking a teammate's agent something, or deciding whether work is already claimed by someone else.
skill-sentinel
Auditoria e evolucao do ecossistema de skills. Qualidade de codigo, seguranca, custos, gaps, duplicacoes, dependencias e relatorios de saude.
haiku
When writing a haiku for this bot, follow these conventions.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
ln-62-repository-publisher
Commits, pushes, and remotely verifies authorized repository changes. Not for releases, package publication, or announcements.