A command that creates a runnable proof-of-concept exploit for a confirmed serious security finding. A proof of concept is a small program that demonstrates the finding is real.

Use it to locate a finding in an audit report, reproduce the named code version, choose a suitable test setup, and produce a one-command runnable exploit.

It turns a written security finding into testable evidence while checking that the required severity and analysis information is present. It also handles missing development tools by reducing the result instead of stopping completely.

auditor:poc — Command for Claude Code by solanabr/auditor-skill

Install

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.

Clone the repo

git clone --depth 1 https://github.com/solanabr/auditor-skill

Made for: Claude Code.

Or install auditor, the plugin that ships this one along with the rest of its 1 skill, 15 commands, 8 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/solanabr/auditor-skill/poc/github.svg)](https://agentmods.dev/commands/solanabr/auditor-skill/poc)

Your own site

<a href="https://agentmods.dev/commands/solanabr/auditor-skill/poc"><img src="https://agentmods.dev/badge/commands/solanabr/auditor-skill/poc/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/solanabr/auditor-skill/poc"><img src="https://agentmods.dev/badge/commands/solanabr/auditor-skill/poc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,357 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.01357
Opus 5.5	$0.00000	$0.00543
Sonnet 5.5	$0.00000	$0.00271
Haiku 4.5	$0.00000	$0.00136

Measured 1mo ago against content hash ae942546fa9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

auditor:poc 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.

commands/poc.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

auditor-skill — Executable Proof-of-Concept

Arguments: $ARGUMENTS

Turn a confirmed finding into a runnable exploit. Read OUTPUT-RULES.md first (severity 1-10, the Rule 5b gate — the finding must already carry a filled Reachability + Math/State-Bounds block, Attacker-Model for N≥7) and references/orchestration/poc-harness.md (the finding-type → framework matrix and the [PoC-*] evidence tiers this command emits). A PoC is evidence that upgrades an asserted finding to a demonstrated one — it never invents a finding that Rule 5b did not already confirm.

Steps

Resolve the finding. Locate the target: a finding id (F-xxx) resolved from the latest audit_<n>/REPORT.md, or a raw file:line. Read its full finding block and its context worksheet under audit_<n>/worksheets/context/* (the reconstructed instruction/state model the PoC will drive). Pin the audited commit the report names — the harness reproduces that commit, not HEAD.
Severity gate. By default only High/Critical (N≥7) findings earn an executable PoC — a runnable exploit is the Rule 5b PoC those severities demand, and spending the harness budget on low-severity items is waste. --force overrides the gate for a deliberately-requested lower-severity demonstration. A finding still at [UNCONFIRMED] / [PARTIAL] is not eligible — confirm it through Rule 5b first.
Detect the toolchain (never assume). Probe what is actually installed:
- cargo build-sbf --version (SBF program build),
- surfpool MCP reachable (mainnet-fork execution),
- trident --version / cargo fuzz --version on PATH (coverage-guided fuzzing). Record which are present. A missing tool is a blocker to name, not a reason to fabricate.
Pick the framework by finding type (matrix in references/orchestration/poc-harness.md):
- logic / access-control / signer / owner / PDA / CPI → Mollusk single-instruction harness (fastest, deterministic, one process_instruction).
- multi-step lifecycle (init → mutate → withdraw, cross-instruction state) → LiteSVM stateful sequence.
- economic / oracle / MEV → Surfpool mainnet-fork (--fork) — reproduce deposit→manipulate→withdraw against forked pool state for a real P/L figure.
- fuzz-discoverable parse / deser / math → Trident / cargo-fuzz (--fuzz) — emit the fuzz target that finds the crashing input. --fork / --fuzz force the Surfpool / fuzz path respectively when the finding type is ambiguous.

Read the full file on GitHub · 52 lines

Changes

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 · 52 lines · 0 tokens per session scan A ae942546fa9a

Subscribe to this mod's changes

auditor:poc is a command published in the GitHub repository solanabr/auditor-skill (59 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,357 tokens. 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.

Security anchor-lang audit-skill claude-skills defi-security pinnochio security-audit

auditor:poc

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

auditor-skill — Executable Proof-of-Concept

Steps

What this file has done since we first saw it

Other commands, from other repositories

wp-perf-review

wp-perf

genshijin-compress

design-form

standup

enum-udp