Borrowing it
Nothing to install: this file belongs to solanabr/solana-vault-standard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/solanabr/solana-vault-standard/main/.claude/commands/cleanup.mdgit clone --depth 1 https://github.com/solanabr/solana-vault-standardWrote 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/solanabr/solana-vault-standard/cleanup)<a href="https://agentmods.dev/commands/solanabr/solana-vault-standard/cleanup"><img src="https://agentmods.dev/badge/commands/solanabr/solana-vault-standard/cleanup/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/solanabr/solana-vault-standard/cleanup"><img src="https://agentmods.dev/badge/commands/solanabr/solana-vault-standard/cleanup.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.00016 | $0.00556 |
| Opus 5 | $0.00008 | $0.00278 |
| Sonnet 5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
cleanup 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 9d 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
Initialize a forked solana-claude-config template for use as a project. Sets up CLAUDE.md and removes config repo scaffolding files.
Step 1: Setup CLAUDE.md
If CLAUDE.md doesn't exist (or contains "Meta Configuration" indicating it's the repo maintainer version):
- Copy
CLAUDE-solana.md→CLAUDE.md - Create starter
CLAUDE.local.md(gitignored, private notes) if it doesn't exist - Add
CLAUDE.local.mdto.gitignoreif not present
If CLAUDE.md already exists and looks like a project config (not meta), skip this step.
Step 2: Create .env if missing
If .env doesn't exist but .env.example does, copy .env.example → .env before removing .env.example.
Step 3: Remove scaffolding
Files/dirs that exist only for maintaining the config repo itself.
Remove (if they exist):
install.sh— installer (not needed after fork)update.sh— deprecation wrappervalidate.sh— config repo validationtests/— config repo test suiteCLAUDE-solana.md— source template (now copied as CLAUDE.md)QUICK-START.md— config repo docsREADME.md— config repo readme (user should write their own).github/workflows/ci.yml— config repo CI (keep claude-code.yml if present).env.example— should already be copied to .env
Preserve (never touch):
.claude/— entire directory (agents, commands, skills, rules, settings, mcp, bin)CLAUDE.md— just created/preserved aboveCLAUDE.local.md— private notes.gitmodules— submodule definitions.env— secrets.gitignore— ignore rulesLICENSE— keep unless user wants to change- Any user-created files
Step 4: Confirm and execute
- Show the user exactly what will happen (CLAUDE.md setup + files to remove)
- Wait for user confirmation before proceeding
- Execute the removals
- Print summary of what was done
- Suggest:
git add -A && git commit -m "chore: initialize project from solana-claude-config template"
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.
- 9d ago First seen · 52 lines · 16 tokens per session scan A 2439279f712f
cleanup is a command published in the GitHub repository solanabr/solana-vault-standard (24 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 556 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-30.
Other commands, from other repositories
auditor:audit-assist
Flow B — AI-assisted iterative audit with a human in the loop. Same lifecycle as audit-cycle, but pauses at checkpoints to surface confirmed findings, the next-focus plan, and targeted questions only the human can answer (business context, trust model, severity calls). The human steers; the agent re-synthesizes toward…
auditor:intake
Interactive engagement intake (alias /scope). Walks QUESTIONS.md and persists the answers to audit /intake.md — the durable intake artifact both audit-cycle and audit-assist read, instead of answers living only in conversation state. Captures scope + commit pin, languages/frameworks, protocol class, compliance…
auditor:economic-sim
Quantify a candidate economic finding — compute attack cost vs extractable value and, when possible, reproduce deposit→manipulate→withdraw against a Surfpool mainnet-fork for a real P/L figure.
deploy
Deploy Solana program (devnet first, then mainnet).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.