solana-vault-standard: Command for Claude Code

.claude/commands/cleanup.md

cleanup is a command for Claude Code from solanabr/solana-vault-standard. It costs 16 tokens per session (556 once invoked), scanned A, original, MIT.

A setup command for turning a copied Solana project configuration template into a working project. Solana is a blockchain platform; the command prepares its agent instructions and local environment files.

In plain words
What is it for?
Use it after copying the template to create CLAUDE.md, preserve private local notes, create .env from .env.example when needed, and remove template-maintainer files.
Why use it?
It removes files used only to maintain the original configuration repository, so the forked project starts with only the files it needs.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is solanabr/solana-vault-standard's own configuration. It tells Claude Code how to work on solana-vault-standard itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything solana-vault-standard configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/solanabr/solana-vault-standard/main/.claude/commands/cleanup.md
Clone the repo
git clone --depth 1 https://github.com/solanabr/solana-vault-standard

Made for: Claude Code.

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.

agentmods badge for cleanup

README.md
[![agentmods](https://agentmods.dev/badge/commands/solanabr/solana-vault-standard/cleanup/github.svg)](https://agentmods.dev/commands/solanabr/solana-vault-standard/cleanup)
Your own site
<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.

agentmods 80×15 button for cleanup

Your own site · 80×15
<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>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 556 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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 2439279f712f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

.claude/commands/cleanup.md · 52 lines

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):

  1. Copy CLAUDE-solana.mdCLAUDE.md
  2. Create starter CLAUDE.local.md (gitignored, private notes) if it doesn't exist
  3. Add CLAUDE.local.md to .gitignore if 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 wrapper
  • validate.sh — config repo validation
  • tests/ — config repo test suite
  • CLAUDE-solana.md — source template (now copied as CLAUDE.md)
  • QUICK-START.md — config repo docs
  • README.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 above
  • CLAUDE.local.md — private notes
  • .gitmodules — submodule definitions
  • .env — secrets
  • .gitignore — ignore rules
  • LICENSE — keep unless user wants to change
  • Any user-created files

Step 4: Confirm and execute

  1. Show the user exactly what will happen (CLAUDE.md setup + files to remove)
  2. Wait for user confirmation before proceeding
  3. Execute the removals
  4. Print summary of what was done
  5. Suggest: git add -A && git commit -m "chore: initialize project from solana-claude-config template"
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.

  1. 9d ago First seen · 52 lines · 16 tokens per session scan A 2439279f712f

Subscribe to this mod's changes

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.