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/commands/beriktassuly/solana-audit-skill/audit-upgrade-migration)<a href="https://agentmods.dev/commands/beriktassuly/solana-audit-skill/audit-upgrade-migration"><img src="https://agentmods.dev/badge/commands/beriktassuly/solana-audit-skill/audit-upgrade-migration/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/beriktassuly/solana-audit-skill/audit-upgrade-migration"><img src="https://agentmods.dev/badge/commands/beriktassuly/solana-audit-skill/audit-upgrade-migration.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.00031 | $0.00329 |
| Opus 5 | $0.00015 | $0.00164 |
| Sonnet 5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
audit-upgrade-migration 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 10d 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
Audit Upgrade Migration
Route first to ../skill/SKILL.md. Load focused references only as needed:
../skill/references/taxonomy/upgrade-admin-governance.md../skill/references/taxonomy/lifecycle-reinit-close-revival.md../skill/references/taxonomy/state-machine-invariants.md../skill/references/workflows/release-gate-workflow.md../skill/references/workflows/formal-verification-handoff.md
Scope
Review account layout changes, versioning, realloc behavior, migration idempotency, rollback limits, authority custody, timelock or governance approvals, fork or localnet simulation, and byte-diff or account-diff evidence.
Required Output
- State whether the migration is a
Confirmed Finding,Hypothesis,Residual Risk, or release-gate blocker. - Map issues to the focused references above.
- Name evidence for account layout compatibility, migration replay or resume behavior, authority and timelock controls, simulation coverage, rollback limits, and post-migration account diffs.
- Treat missing evidence for a required mainnet migration check as release-gate
FAIL.
Verification Targets
Prefer fork/localnet simulation against representative live accounts, pre/post account-diff review, byte-diff or build provenance checks, negative tests for repeated migration, and explicit rollback or pause drills where the trust model requires them.
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.
- 10d ago First seen · 30 lines · 31 tokens per session scan A 7cfce9ad248f
audit-upgrade-migration is a command published in the GitHub repository beriktassuly/solana-audit-skill (4 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 329 once invoked, about $0.0002 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 commands, from other repositories
scan
Scan a path against the Solana Security Standard (SOL-0XX) and report findings with fixes.
krait-fuzz
Run an invariant-based fuzzing campaign: Understand → Extract Invariants → Generate Foundry Tests → Run & Fix Iteratively → Report.
krait-poc
Write and run a valid Foundry proof-of-concept that proves (or disproves) a Solidity exploit by asserting the actual harm on a forked chain or against local source.
setup-x402
Wire x402 pay-per-call onto a provider's already-comprehended API via PayAI — point tools at the provider's OWN x402 endpoint, prove the handshake offline (X402MODE=stub), keep the provider at 100%. Gecko never the rail, no cut. Usage: /setup-x402.
krait-quick
Run a streamlined audit: Recon → Detection → Verification → Report. Skips state inconsistency analysis and cross-feed iteration for speed.
audit-strict
Multi-pass consensus audit — runs the audit twice with different prompts, only reports consensus findings. Aggressively cuts false positives.