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/cloudnative-co/claude-code-starter-kit/audit-configgit clone --depth 1 https://github.com/cloudnative-co/claude-code-starter-kitWhat 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.00019 | $0.00559 |
| Opus 5 | $0.00010 | $0.00280 |
| Sonnet 5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
audit-config 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 2d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit-config — Personal Config Audit
Audit user-owned configuration for instructions that no longer help (or actively hurt) current-generation models. Kit-managed files are NOT in scope — the kit audits its own content upstream.
Scope
global(default): the user section of~/.claude/CLAUDE.md(content outside the STARTER-KIT-MANAGED markers) and user-owned rule files (~/.claude/rules/user-*.mdand any rules file not shipped by the kit)project: the current project'sCLAUDE.md/.claude/configall: both
Audit Lenses
Classify each instruction (line or section) into:
- babysitting — countermeasures for old-model failure modes that no longer occur (e.g. tool-call format reminders, "fix errors immediately", forced step-by-step rituals)
- over-prescription — rigid procedures that override the model's own judgment where it is now reliable (blanket TDD/coverage mandates, fixed command pipelines, arbitrary numeric gates)
- stale-premise — references to old models, retired features, or superseded mechanics (thinking keywords, old model names, obsolete context-management lore)
- context-tax — always-loaded lines duplicating what the harness or settings already enforce (language settings, parallel tool calls, risk reporting). Verify the duplication against the actual settings file or documented harness behavior before claiming it — cite what you checked.
Preservation Rules (do not over-delete)
- Genuine personal preferences stay. Anything the model could not infer on its own — naming/secrecy rules, confirmation gates, response formats, workflow phrases — is the user's voice, not babysitting.
- When unsure whether something is preference or babysitting, keep it and say why you were unsure.
- Only mark
context-taxremovals when you actually verified the duplication (e.g. readsettings.json, confirmed the harness ships the behavior). No speculation-based deletions.
Output (proposal only — never edit without approval)
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.
- 2d ago First seen · 56 lines · 19 tokens per session scan A 3bb55042c967
audit-config is a command published in the GitHub repository cloudnative-co/claude-code-starter-kit (147 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 559 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
claude-flow-swarm
Coordinate multi-agent swarms for complex tasks.
advisor
Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.
bootstrap
PACT session-start ritual — identify the session team (platform-provisioned), secretary spawn, paused-state surface, bootstrap marker.
ox-session-review
Command "ox-session-review" from sageox/ox, covering failure-mode watch-list (read first), from the ledger root. should print 0, phase 1 — scan & score (read-only), quality buckets (first match wins) and removal candidates.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.