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.
npx agentmods add commands/solanabr/solana-ai-kit/setup-mcpgit 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/setup-mcp)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/setup-mcp"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/setup-mcp.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.00008 | $0.00450 |
| Opus 5 | $0.00004 | $0.00225 |
| Sonnet 5 | $0.00002 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade C, and why
setup-mcp scanned grade C with 2 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 6d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
**Note — Surfpool MCP is keyless** (no `.env` entry), but its server (`surfpool mcp`) requires the `surfpool` CLI binary on PATH. Install is the user's responsibility — do not run it for them: `curl -L https://surfpool.r Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Note — Surfpool MCP is keyless** (no `.env` entry), but its server (`surfpool mcp`) requires the `surfpool` CLI binary on PATH. Install is the user's responsibility — do not run it for them: `curl -L https://surfpool.r What it actually says
You are guiding the user through MCP API key setup. All secrets go in .env (never in mcp.json).
Step 1: Ensure .env exists
Check if .env exists in the project root. If not, copy from .env.example:
if [ ! -f ".env" ] && [ -f ".env.example" ]; then
cp .env.example .env
echo "Created .env from .env.example"
elif [ ! -f ".env" ]; then
touch .env
echo "Created empty .env"
else
echo "Found existing .env"
fi
Step 2: Configure secrets
For each key below, ask the user to paste a value or say "skip":
- HELIUS_API_KEY — Helius RPC + DAS API (get one at https://dev.helius.xyz)
- COLOSSEUM_COPILOT_PAT — Colosseum Copilot for startup research (optional, get at https://arena.colosseum.org/copilot)
- MISTRAL_API_KEY — QEDGen formal verification (optional, get at https://console.mistral.ai)
For each value provided, write or update the line in .env. Skip means leave it empty.
Note — Surfpool MCP is keyless (no .env entry), but its server (surfpool mcp) requires the surfpool CLI binary on PATH. Install is the user's responsibility — do not run it for them: curl -L https://surfpool.run/install | sh or brew install txtx/taps/surfpool. Verify with command -v surfpool.
Step 3: Summary
Print which keys are configured vs skipped:
MCP secrets (.env):
HELIUS_API_KEY [configured / skipped]
COLOSSEUM_COPILOT_PAT [configured / skipped]
MISTRAL_API_KEY [configured / skipped]
Remind the user: restart Claude Code to pick up 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.
- 6d ago First seen · 47 lines · 8 tokens per session scan C c29517546a72
setup-mcp is a command published in the GitHub repository solanabr/solana-ai-kit (99 stars, last pushed 16d ago), licensed MIT. It adds 8 tokens to every session and 450 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
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.
apex-quick
Quick Flow for simple fixes - Single expert handles explore, code, review, and validate in one pass. Inspired by BMAD Barry.
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.
fix-pr-comments
Systematically resolve Pull Request review comments using gh CLI to fetch comments and apply requested changes.