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 skills/blockrunai/blockrun-mcp/blockrun-setupnpx skills add BlockRunAI/blockrun-mcp --skill blockrun-setupgit clone --depth 1 https://github.com/BlockRunAI/blockrun-mcpWrote 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/skills/blockrunai/blockrun-mcp/blockrun-setup)<a href="https://agentmods.dev/skills/blockrunai/blockrun-mcp/blockrun-setup"><img src="https://agentmods.dev/badge/skills/blockrunai/blockrun-mcp/blockrun-setup.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 | $0.00093 | $0.01619 |
| Opus 5 | $0.00046 | $0.00809 |
| Sonnet 5 | $0.00019 | $0.00324 |
| Haiku 4.5 | $0.00009 | $0.00162 |
Grade B, and why
blockrun-setup scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Codex CLI** (`--env` is Codex's equivalent of `-e`; config lands in `~/.codex/config.toml`): How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Installing BlockRun MCP
One command per client, then one tool call to see the wallet. Do it in this order; the PATH step is the one people skip and then spend an hour on.
1. Check Node first
node -v # must print v20.19 or newer
which npx
If node is from nvm, Homebrew, fnm, volta or asdf, assume the client's launcher
will NOT find it. GUI-launched apps and Claude Code's MCP spawner do not source your
shell profile. The fix is to pass your shell's PATH through at install time — not to
pin nvm alias default, not to edit .zshrc, not to symlink node into /usr/local/bin.
2. Install — pick the client
Claude Code (recommended; -s user = every project):
claude mcp add blockrun -s user -e PATH="$PATH" -- npx -y @blockrun/mcp@latest
The -- matters: it stops -y being parsed by claude mcp add. The -e PATH="$PATH"
is the nvm/Homebrew fix from step 1; it is harmless on a system Node, so always include it.
Codex CLI (--env is Codex's equivalent of -e; config lands in ~/.codex/config.toml):
codex mcp add blockrun --env PATH="$PATH" -- npx -y @blockrun/mcp@latest
Claude Desktop / Cursor / Windsurf — JSON, in the client's MCP config file:
{ "mcpServers": { "blockrun": { "command": "npx", "args": ["-y", "@blockrun/mcp@latest"] } } }
| Client | File |
|---|---|
| Claude Desktop | claude_desktop_config.json (Settings → Developer → Edit Config) |
| Cursor | ~/.cursor/mcp.json · Windows %APPDATA%\Cursor\mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json · Linux ~/.config/.codeium/windsurf/mcp_config.json |
For a JSON client with nvm/Homebrew Node, put the absolute npx path (which npx) in
command — there is no -e PATH equivalent there.
Optional flags (append after @latest): --profile trading|research|media|chat
exposes a smaller tool set so the client loads fewer schemas. Omit for all 20 tools.
Optional env (-e KEY=value on Claude Code, "env": {} in JSON):
BLOCKRUN_CONFIRM_SPEND=on asks before each paid call on clients that support MCP
elicitation; BLOCKRUN_CONFIRM_THRESHOLD=0.05 limits that to calls above $0.05;
BLOCKRUN_BUDGET_LIMIT=5 hard-caps the process at $5.
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.
- 3d ago First seen · 123 lines · 93 tokens per session scan B 48726a06d3a8
blockrun-setup is a skill published in the GitHub repository BlockRunAI/blockrun-mcp (393 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 1,619 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
fetcher
Shared payment and setup skill for fetcher.sh, a pay-per-call web-data API covering Twitter/X, TikTok, Instagram, YouTube, Reddit, Google Search, Google Maps, Google News, Google Play, the App Store, and Yelp. Use this skill whenever a task needs a fetcher.sh API key, a credit top-up, an x402 micropayment, MCP server…
x402-payments
Quote and settle OpenMesha x402 paywalled services (USDC on Base). Use when metering tool calls, outcome fees, or agent-to-agent settlement.
x402-payments
Work with Server OS micropayment (x402) capabilities for agents.
Government Tender Search
Search 11,000+ active government contracts from CanadaBuys and SAM.gov via ONE-1 x402 API.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…