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/solanabr/auditor-skillWrote 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/solanabr/auditor-skill/diff-audit)<a href="https://agentmods.dev/commands/solanabr/auditor-skill/diff-audit"><img src="https://agentmods.dev/badge/commands/solanabr/auditor-skill/diff-audit/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/solanabr/auditor-skill/diff-audit"><img src="https://agentmods.dev/badge/commands/solanabr/auditor-skill/diff-audit.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.00049 | $0.00581 |
| Opus 5.5 | $0.00020 | $0.00232 |
| Sonnet 5.5 | $0.00010 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
auditor:diff-audit 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.
What it actually says
auditor-skill — Differential Audit (Mode 4)
Arguments: $ARGUMENTS
- Compute the changed set:
git diff --name-only <base>..<head>(defaultmain..HEAD). In a checkout you did not clone yourself, every git call carries theOUTPUT-RULES.mdRule 11c flags. - Run Phase 0.5 Context Reconstruction on changed functions + their direct callers/callees (1-hop).
- Risk-classify changed files (auth / crypto / value-transfer / validation-removal = HIGH). Git-blame removed security code (in a checkout you did not clone:
GIT_NO_LAZY_FETCH=1 git --no-pager -c core.fsmonitor=false -c log.showSignature=false blame --no-textconv --no-ext-diff <rev> -- <path>, Rule 11c) — code deleted in a "fix" / "CVE" commit is a CRITICAL regression. - Run only the checklist items + known-vectors matching the changed files' language/domain, through the Rule 5b gate.
- Dependency lane. If the changed set touches a manifest or lockfile (
Cargo.toml,Cargo.lock,package.json,package-lock.json,npm-shrinkwrap.json,pnpm-lock.yaml,yarn.lock,bun.lock,pyproject.toml,uv.lock,poetry.lock,requirements*.txt,go.mod,go.sum), run checklist 11 §11.11 on the dependency delta. Baseline: this run's<base>..<head>; a re-audit passes the last audited ref as<base>. Enumerate every changed entry, artifact-diff what the §11.11 coverage budget names — fetched from the registry, never installed or built — and verdict SC-059..062, stating how many changed packages were left without an artifact diff. A one-line lockfile bump can bring in a whole new release, so the changed lines alone are not the reviewed code. - Emit
audit_<n>/PR-REPORT.md— changed-surface verdicts + findings only, plus a Dependency delta section when step 5 ran. Reuses the methodology corpus; skips whole-repo discovery. Output hygiene and any outside-service disclosure followOUTPUT-RULES.mdRule 11d / 11b.
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 Changed de9ac669f8c6
- 3d ago Changed · +1 lines · +9 tokens per session 4e5d81e7581f
- 1mo ago First seen · 17 lines · 40 tokens per session scan A 4bd258b578bb
auditor:diff-audit is a command published in the GitHub repository solanabr/auditor-skill (61 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 581 once invoked, about $0.0002 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-30.
Other commands, from other repositories
genshijin-review
A compact Japanese-language code-review command that reports one finding per line with a severity label and suggested fix.
review
Recent git commits: !git log --oneline -10.
review-open-prs
Command "review-open-prs" from The-Artificer-of-Ciphers-LLC/skills-from-the-artificer, covering batch pr review directive — all open prs i did not author, phase a — enumerate target prs & build the queue, phase b — per-pr directive (runs once per queued $pr), 0. context anchoring and 1. preconditions.
snr-build
Architect and scaffold a new project to senior professional standards, in the order that avoids expensive retrofits.
resolve-review
Resolve reviewer feedback - from GitHub PRs, chat, or any reviewer.
setup
Set up, configure, or reconfigure notabene and start the docs review server.