Borrowing it
Nothing to install: this file belongs to solanabr/solana-glossary. 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-glossary/main/.claude/commands/setup-mcp.mdgit clone --depth 1 https://github.com/solanabr/solana-glossaryWrote 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-glossary/setup-mcp)<a href="https://agentmods.dev/commands/solanabr/solana-glossary/setup-mcp"><img src="https://agentmods.dev/badge/commands/solanabr/solana-glossary/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.00366 |
| Opus 5 | $0.00004 | $0.00183 |
| Sonnet 5 | $0.00002 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
setup-mcp 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 8d 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.
This is a copy
100% identical to setup-mcp — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
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.
- 8d ago First seen · 45 lines · 8 tokens per session scan A 3cea81b3742a
setup-mcp is a command published in the GitHub repository solanabr/solana-glossary (18 stars, last pushed 27d ago), licensed MIT. It adds 8 tokens to every session and 366 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to setup-mcp, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
ingest-dev
Ingest a URL, directory, or file into your knowledge base. remember = a specific durable fact, ingest = a URL, learn = a distilled lesson that gets retrieval preference.
resume
Auto-detect and resume any interrupted Plan Cascade task. Detects mega-plan, hybrid-worktree, or hybrid-auto context and routes to the appropriate resume command.
review-video
Make a " Reviews" video — a fast, faceless VO montage of REAL, verified competitor reviews that names the recurring complaints and positions YOUR business as the alternative, then hands off to your own customer testimonials.
next
You just finished a slash command or a batch of work. The user monitors via Farmer on their phone and cannot see CLI text output.