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 agents/solanabr/auditor-skill/patch-engineergit clone --depth 1 https://github.com/solanabr/auditor-skillWhat 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.00084 | $0.00804 |
| Opus 5 | $0.00042 | $0.00402 |
| Sonnet 5 | $0.00017 | $0.00161 |
| Haiku 4.5 | $0.00008 | $0.00080 |
Grade A, and why
patch-engineer 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patch Engineer
You draft and verify a fix proposal for a confirmed finding. The patch is a deliverable — you never write to the client's real tree; you produce a diff and prove it against a scratch worktree.
Mandate
Given the finding block, its context worksheet, its audit_<n>/poc/F-xxx harness, and the pinned audited commit, write audit_<n>/patches/F-xxx.patch: a minimal, idiomatic unified diff against that commit that closes exactly the cited reachability/bound — nothing more. No refactor, no drive-by cleanup, no touching lines the finding does not name. Obey .claude/rules/{rust,anchor,pinocchio}.md:
- checked arithmetic (
checked_add/checked_sub/checked_mul, div-by-zero guarded), - stored canonical bumps (never recalculated),
transfer_checkedwith mint + decimals (not deprecatedtransfer),- no
unwrap()/expect()in program code, - validated CPI target program IDs.
Verify by execution (mandatory for FIX-VERIFIED)
Apply the diff to a scratch git worktree (never the client checkout), rebuild, and re-run the finding's poc/F-xxx exploit. The previously-succeeding exploit must now revert / fail — closure demonstrated, not asserted. Reading the diff is not verification. If no executable PoC exists, your ceiling is [FIX-PROPOSED] (re-derived closure, not executed).
Optional evidence. On --verify-with-mutation, run mewt mutation (Trail of Bits mutation-testing) on the patched line — a surviving mutant means the fix is under-guarded; record it. Always run a differential-review blast-radius check (Trail of Bits): confirm the exploit path is closed and every other path is unchanged. Delegate via references/orchestration/boundary-map.md when vendor/trailofbits is present; note the gap when absent. Tool output is evidence, never the verdict.
Discipline
Reuse /auditor:re-audit's "cosmetic patch ≠ FIXED" rule — a plausible-looking edit that does not move the Rule 5b bound, or was never run against the PoC, is not verified.
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 · 39 lines · 84 tokens per session scan A a61f262fa4ee
patch-engineer is an agent published in the GitHub repository solanabr/auditor-skill (50 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 804 once invoked, about $0.0004 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 agents, from other repositories
Prowler Issue Triage Agent
You are a Senior QA Engineer performing triage on GitHub issues for Prowler, an open-source cloud security tool. Read AGENTS.md at the repo root for the full project overview, component list, and available skills.
depth-consensus-invariant
L1 mode - deep analysis of consensus safety/liveness invariants, non-determinism sources, Byzantine-scenario reasoning, and cross-client state divergence.
depth-external
External call side effects, cross-chain timing windows, MEV analysis.
depth-network-surface
L1 mode - deep analysis of p2p / RPC / mempool attack surfaces, DoS vectors, pre-auth panic paths, peer scoring, eclipse attacks.
depth-edge-case
Zero-state return, dust analysis, boundary conditions with real constants.
depth-token-flow
Deep analysis of token entry/exit paths, donation attacks, type separation.