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/xiaolai/cc-suite/audit-fixgit clone --depth 1 https://github.com/xiaolai/cc-suiteWrote 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/xiaolai/cc-suite/audit-fix)<a href="https://agentmods.dev/commands/xiaolai/cc-suite/audit-fix"><img src="https://agentmods.dev/badge/commands/xiaolai/cc-suite/audit-fix.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 | $0.00022 | $0.03639 |
| Opus 5 | $0.00011 | $0.01819 |
| Sonnet 5 | $0.00004 | $0.00728 |
| Haiku 4.5 | $0.00002 | $0.00364 |
Grade A, and why
audit-fix 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.
How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
What This Does
Runs a complete audit→fix→verify cycle:
- Audit — find issues (full 9-dimension or mini 5-dimension)
- Fix — Claude fixes by default (or Codex with
--fixer=codex) - Verify — check that each fix actually resolved the issue
- Repeat — if issues remain, loop back to fix
Continues until all issues are resolved or the user decides to stop.
Arguments
By default this command runs non-interactively: fixes all findings using Claude, and stops at the end of the first round if any issues remain. Override the defaults with flags, or pass --ask to restore the interactive prompts.
--severity=all|high— which findings to fix (defaultall).highmeans "High severity and above": Critical+High on a full audit, High-only on a mini audit.--fixer=claude|codex— who applies the fix (defaultclaude).--ask— show interactiveAskUserQuestionprompts for fix scope, fixer choice, and the partial-iteration continue/switch decision.
The danger-full-access sandbox warning below is always shown regardless of --ask.
Model & Settings Selection
Follow the instructions in commands/shared/model-selection.md to discover available models and present choices.
- Recommended model: first available from preflight
- Recommended reasoning effort:
high - Recommended sandbox level:
workspace-write - Include sandbox question: Yes (fixes require write access)
Warning: If the user selects
danger-full-accesssandbox, display a confirmation before proceeding: "You chosedanger-full-accesswith no approval prompts — Codex will have unrestricted access. Continue?" UseAskUserQuestionwith "Continue" and "Switch to workspace-write" options.
Workflow
Step 1: Determine audit type and scope
Follow the audit type selection logic in commands/audit.md Step 1 to parse --full/--mini flags from $ARGUMENTS, check {config_default_audit_type}, and ask the user if neither is set.
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.
- 4d ago First seen · 310 lines · 22 tokens per session scan A 7550f8834044
audit-fix is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 2d ago), licensed ISC. It adds 22 tokens to every session and 3,639 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.