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/solanabr/solana-ai-kitWrote 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-ai-kit/cleanup)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/cleanup"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/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-ai-kit/cleanup"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/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.00021 | $0.00532 |
| Opus 5.5 | $0.00008 | $0.00213 |
| Sonnet 5.5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
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 25d 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
Turn a fork or clone of the solana-ai-kit repo into a working project: install the project CLAUDE.md and delete the files that only serve maintaining or publishing the kit.
Steps
- CLAUDE.md. If it is missing, or is the maintainer version (contains "Meta Configuration"), copy
CLAUDE-solana.mdtoCLAUDE.md, create a starterCLAUDE.local.mdfor private notes if absent, and addCLAUDE.local.mdto.gitignore. Leave an existing projectCLAUDE.mdalone. - .env. If
.envis missing and.env.exampleexists, copy.env.exampleto.envbefore anything is removed. - Plan the removals, each only if present (a missing path is not an error):
- Maintenance:
install.sh,update.sh(deprecation wrapper),validate.sh,tests/,CLAUDE-solana.md,QUICK-START.md,README.md(the kit's; the user writes their own),.claude/CHANGELOG.md(the kit's changelog),.github/workflows/ci.yml(keep.github/templates/claude-code.yml) - Distribution infra, only needed to publish the kit:
.claude-plugin/(plugin marketplace manifest),plugin/(symlinked plugin subtree),vercel.json(install-endpoint redirect) - Keep: the rest of
.claude/(agents, commands, skills, settings,bin/self-update tooling),CLAUDE.md,CLAUDE.local.md,.mcp.json,.env,.env.example(the tracked list of keys that/setup-mcpand/doctorread),.gitmodules,.gitignore,LICENSE(unless the user wants another), and anything the user created. If another file looks kit-specific, flag it instead of deleting it.
- Maintenance:
- Confirm. Show the CLAUDE.md action and the exact removal list, and wait for the user's go-ahead.
- Execute, print a summary of what was done, and suggest
git add -A && git commit -m "chore: initialize project from solana-ai-kit 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.
- 25d ago Changed · -45 lines · +5 tokens per session 50f355c30c37
- 26d ago Changed · +1 lines 54e87b8a52a1
- 1mo ago First seen · 63 lines · 16 tokens per session scan A 66ae75873543
cleanup is a command published in the GitHub repository solanabr/solana-ai-kit (104 stars, last pushed 26d ago), licensed MIT. It adds 21 tokens to every session and 532 once invoked, about $0.0001 per session on Opus 5.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
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
explain-architecture
Analyze and explain software architecture with ASCII diagrams and pattern detection. Creates visual representations of system design.
prompt
Create or optimize prompts using best practices.
watch
Check for Claude Code updates, detect breaking changes, analyze plugin compatibility, and optionally gather community pulse via Exa.
design-audit
Audit an existing HTML/CSS design. Deterministic checks only (contrast, fonts, colors, states, dark mode) plus a visual pass. No generation.
fix-pr-comments
Systematically resolve Pull Request review comments using gh CLI to fetch comments and apply requested changes.