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.
git clone --depth 1 https://github.com/xcodethink/open-claude-code-skillsWrote 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/xcodethink/open-claude-code-skills/audit-fix)<a href="https://agentmods.dev/commands/xcodethink/open-claude-code-skills/audit-fix"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/audit-fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/xcodethink/open-claude-code-skills/audit-fix"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/audit-fix.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.00290 |
| Opus 5.5 | $0.00011 | $0.00116 |
| Sonnet 5.5 | $0.00006 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
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 1mo 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
audit-fix — 审计后批量修(根因分组)
用户输入 /audit-fix $ARGUMENTS 触发 根因分组批量修。
立刻读取并完整加载:
~/.claude/prompts/lib/02-诊断/审计批量修.md
按其"行为契约"段严格执行:
- 先分组 — 哪些问题可能是同一个根因 → 按根因分组,不是逐条修
- 每组先做完整 5 步诊断(参照
stuck-bug流程) - 输出"分组修复计划"等用户 yes
- 每组改完跑全量回归确认
- 不允许"先改最明显的看看"
参数含修饰符 → 叠加对应文件。
核心契约:见一个改一个 → 根因不收敛,反复来回修。强制根因分组 + 一次改完。
参数: $ARGUMENTS
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.
- 1mo ago First seen · 25 lines · 0 tokens per session scan A 676337b75104
audit-fix is a command published in the GitHub repository xcodethink/open-claude-code-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 290 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
codebase-review
Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
harness-audit
Run a deterministic repository harness audit and return a prioritized scorecard.
debug
Systematic debugging with hypotheses and evidence gathering.
verify
An embedded-device verification workflow that checks a development step through building, flashing firmware, debugging with J-Link, and reading serial logs. Firmware is software that runs directly on a microcontroller or other device.
improve
/improve Scan and fix all improvement categories /improve arch Architectural improvements only /improve duplication Duplicate code / abstraction consolidation /improve quality Code quality (GuardLoop patterns GL-01 through GL-10) /improve security Security posture improvements /improve --dry-run Show what would be…