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 SienkLogic/plan-build-run --skill audit-fixgit clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote 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/sienklogic/plan-build-run/audit-fix)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/audit-fix"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/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/skills/sienklogic/plan-build-run/audit-fix"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/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.00022 | $0.02265 |
| Opus 5.5 | $0.00009 | $0.00906 |
| Sonnet 5.5 | $0.00004 | $0.00453 |
| Haiku 4.5 | $0.00002 | $0.00227 |
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.
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes tokens. Begin executing Step 0 immediately.
/pbr:audit-fix -- Autonomous Audit-to-Fix Pipeline
You are running the audit-fix skill. Your job is to run a session audit, parse findings, classify which are auto-fixable, and spawn executor agents to fix them one-by-one with atomic commits. The pipeline stops on the first test failure.
This skill chains audit -> prioritize -> fix -> test -> commit in a single command.
Step 0 -- Immediate Output
Before ANY tool calls, display this banner:
+--------------------------------------------------------------+
| PLAN-BUILD-RUN > AUDIT-FIX |
+--------------------------------------------------------------+
Then proceed to Step 1.
Context Budget
Reference: skills/shared/context-budget.md for the universal orchestrator rules.
Reference: skills/shared/agent-type-resolution.md for agent type fallback when spawning Task() subagents.
Additionally for this skill:
- Delegate ALL code changes to executor subagents -- do NOT make fixes yourself
- Main context handles: argument parsing, audit orchestration, finding classification, executor dispatch, reporting
- Read only the audit report findings section, not full session details
- Target: main context stays under 25% utilization
Step 1 -- Parse Arguments
Parse $ARGUMENTS for:
| Argument | Default | Description |
|---|---|---|
--max N |
5 | Maximum number of findings to fix |
--severity LEVEL |
medium |
Minimum severity threshold: high = Critical+High only, medium = +Medium, all = +Low |
--dry-run |
false | List fixable findings without executing fixes |
--from DATE |
Start of today | Passed through to audit agent |
--to DATE |
Now | Passed through to audit agent |
--today |
true (default) | Shorthand for today's audit window |
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 · 327 lines · 22 tokens per session scan A f336bceaf8f1
audit-fix is a skill published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 2,265 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-09-03.
Other skills, from other repositories
eval-hooks
Audit Claude Code and Codex hooks for validity, safety, and correctness across settings.json, hooks.json, config.toml, plugin, and skill or agent frontmatter hooks. Resolves each command, checks event names, handler types, matchers, exit-code and JSON decision strategy, and timeouts against each host's documented…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
sandbox-unblock
Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change. Eleven checks that eliminate false positives, then a report template the person holding the settings can act on. On one measured day, six of eight reported blockers turned out to be false, all from the same handful of…
investigate
Systematic root-cause debugging: find the cause before writing any fix.
qa
Systematic QA testing of a web application: diff-aware, tiered, with fix-and-verify loop.