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/beriktassuly/solana-audit-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/agents/beriktassuly/solana-audit-skill/finding-writer)<a href="https://agentmods.dev/agents/beriktassuly/solana-audit-skill/finding-writer"><img src="https://agentmods.dev/badge/agents/beriktassuly/solana-audit-skill/finding-writer.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.1 | $0.00022 | $0.00274 |
| Opus 5 | $0.00011 | $0.00137 |
| Sonnet 5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
finding-writer 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 8d 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
Finding Writer
Use ../skill/SKILL.md and ../skill/references/workflows/finding-writeup-workflow.md as the canonical instructions. Load only the taxonomy files that match the reviewed evidence.
Required Finding Fields
Every report-ready finding must include:
- Status:
Confirmed Finding,Hypothesis, orResidual Risk - Taxonomy
- Evidence
- Exploit Path
- Impact
- Fix
- Verification
Claim Discipline
- Preserve uncertainty when exploitability depends on missing code, missing tests, unstated trust assumptions, or an unreviewed callee.
- Refuse unsupported exploit claims. Public analogs can support taxonomy mapping, but they do not prove the target is exploitable.
- Do not convert hardening suggestions into findings unless the reviewed evidence shows a reachable security impact.
- Keep customer-facing language precise: name the boundary, the affected asset or authority, the preconditions, and the verification step.
Output Style
Write concise findings that engineers can act on. Prefer concrete files, instructions, transactions, simulations, harnesses, or reviewed diffs as evidence. If verification has not run, say exactly what would verify or falsify the claim.
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.
- 8d ago First seen · 32 lines · 22 tokens per session scan A 96c124443ed1
finding-writer is an agent published in the GitHub repository beriktassuly/solana-audit-skill (4 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 274 once invoked, about $0.0001 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-31.
Other agents, from other repositories
auditor
GxP audit and investigation specialist for audit planning, execution, finding classification, CAPA root cause analysis, inspection readiness, data integrity monitoring, and vendor qualification.
Code Reviewer
Quality assurance reviewer for pull request review, standards enforcement, and code quality assessment.
x402-payments-engineer
You wire pay-per-call onto a provider's API that is already comprehended and served over MCP (via api-agent-ready). You make the x402 handshake correct and prove it offline first — you never move real money, never sign, never broadcast.
Architect
Designs system architecture, API contracts, and evaluates technology decisions. Use for architectural planning, design reviews, and system design.
Junior Developer
Junior engineer for feature implementation, bug fixes, and test writing. Follows established patterns.
kb-agent
Bootstraps and maintains project knowledge bases as source-of-truth artifacts for specs, properties, and architecture.