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 instructions/solanabr/auditor-skill/agents-mdgit 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/instructions/solanabr/auditor-skill/agents-md)<a href="https://agentmods.dev/instructions/solanabr/auditor-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/solanabr/auditor-skill/agents-md.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.00890 | $0.00890 |
| Opus 5 | $0.00445 | $0.00445 |
| Sonnet 5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
auditor-skill AGENTS.md 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 — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
auditor-skill — Agent Orchestration
This skill audits with a small team of subagents (see agents/) and, when available,
orchestrates Trail of Bits execution tooling vendored at vendor/trailofbits.
Flow (full audit)
- Pre-scan (optional, deterministic). If
tools/auditor-tools/is built,audit-scanemits the instruction/constraint/PDA/arithmetic map at ~$0 andaudit-mem warm <program-id>loads prior invariants + open false-positive rulings — seedingcontext-builderwith a map instead of a blank repo, and lettingvuln-hunterauto-suppress findings that carry a priorFALSE_POSITIVEruling (audit-mem check). Falls back to the grep walk if the toolchain is absent. See references/orchestration/pre-scan.md. context-builder(sonnet) — Phase 0 setup + Phase 0.5 context reconstruction. No verdicts; understanding only. 1b.threat-modeler(opus) — from the context worksheets +audit_<n>/intake.md, emitsaudit_<n>/threat-model.md(asset inventory · actor×capability · trust boundaries) that hands the reviewers attacker goals and seeds report §4.4/§4.6/§4.7. No verdicts.vuln-hunter(opus) — item-by-item walk against in-scope checklists + phase-triggered vectors. Every finding with N ≥ 6 must pass the Rule 5b gate. Delegates SAST / harnesses to Trail of Bits when present (seereferences/orchestration/boundary-map.md).economic-analyst(opus) — checklist 06 + economic vectors; drives/economic-sim(Surfpool mainnet-fork) to quantify profitability for High/Critical economic findings.peer-reviewer(opus) — independent reconciliation on top-severity findings (N≥8, contested N≥7): re-derives from the code (reusing the context worksheets), delegates to Trail of Bitssecond-opinion/fp-checkwhen present; emits CONFIRM / DISPUTE / DOWNGRADE. (Neodyme independent dual-review.)audit-reporter(sonnet) — deterministic assembly: Scope Coverage, findings, Phase 4.5 maturity scorecard, remediation roadmap →audit_<n>/REPORT.md.
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 · 25 lines · 890 tokens per session scan A d45004677e1f
auditor-skill AGENTS.md is an instructions file published in the GitHub repository solanabr/auditor-skill (52 stars, last pushed 1mo ago), licensed MIT. It adds 890 tokens to every session, about $0.0044 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 instructions, from other repositories
orquestra copilot-instructions.md
Instructions for berkayoztunc/orquestra, covering copilot instructions — orquestra, project overview, architecture, key patterns & conventions and worker route structure.
solana-vault-standard CLAUDE.md
Instructions for solanabr/solana-vault-standard, covering solana tokenized vault standard, communication style, branch workflow, mandatory workflow and security principles.
evmole AGENTS.md
Instructions for cdump/evmole: EVMole extracts structured facts from deployed EVM runtime bytecode.
plamen CLAUDE.md
Claude Code instructions for PlamenTSV/plamen, covering plamen — security auditor, execution model, reference files and shared.
bray AGENTS.md
AGENTS.md instructions for forgesworn/bray, covering agents.md — nostr-bray, what this is, build & test, architecture and tool groups.
bitcoin-mcp copilot-instructions.md
Instructions for Bortlesboat/bitcoin-mcp, covering bitcoin-mcp copilot instructions, rules, satoshi api reference and verification.