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/setup-mcp.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/setup-mcp)<a href="https://agentmods.dev/commands/solanabr/solana-vault-standard/setup-mcp"><img src="https://agentmods.dev/badge/commands/solanabr/solana-vault-standard/setup-mcp/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/setup-mcp"><img src="https://agentmods.dev/badge/commands/solanabr/solana-vault-standard/setup-mcp.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.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.
Copies of this mod
1 near-identical copy found in the catalogue:
- setup-mcp — 100% identical, 0 lines differ
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-vault-standard (23 stars, last pushed 5mo 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. 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-cycle
Flow A — fully automated audit-firm lifecycle. Runs scope → context → tool-assisted first pass → domain-partitioned manual review → independent reconciliation → client report end-to-end, and delivers a professional audit report (MD + optional PDF). Audit-shaped automation, not a substitute for a human firm audit.
auditor:re-audit
Fix-review / re-audit. Takes a prior audit report + the current tree and classifies every prior finding FIXED / PARTIALLY-FIXED / STILL-OPEN / REGRESSED / ACKNOWLEDGED / DISPUTED (re-running Rule 5b on the fix, citing the remediation commit/PR hash), audits the changed surface for NEW findings via the diff-audit path…
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:poc
Generate an executable proof-of-concept exploit for a confirmed High/Critical finding — detect the toolchain, pick the harness framework by finding type, spawn poc-engineer, and emit a one-command runnable crate plus the earned [PoC-] evidence tier. Never hard-fails: on toolchain absence it downgrades to…
auditor:triage
Re-runnable batch triage checkpoint over the candidate finding set (fixes triage being diffused across agents). Dedups by root-cause signature (reusing /re-audit's signature idea; audit-mem auto-suppresses prior-ruled false positives and flags regressions when built), enforces Rule 5b calibration (every N≥6 carries…
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…