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/crypto-datanpx skills add BlockRunAI/blockrun-mcp --skill crypto-datagit 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/crypto-data)<a href="https://agentmods.dev/skills/blockrunai/blockrun-mcp/crypto-data"><img src="https://agentmods.dev/badge/skills/blockrunai/blockrun-mcp/crypto-data.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.00170 | $0.02840 |
| Opus 5 | $0.00085 | $0.01420 |
| Sonnet 5 | $0.00034 | $0.00568 |
| Haiku 4.5 | $0.00017 | $0.00284 |
Grade A, and why
crypto-data 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crypto Data
Five tools cover crypto data and they overlap. Pick by cost first — two of them are free, and paying for a quote you could get for nothing is the most common mistake here.
Route by cost — check this before calling anything
| Question | Tool | Cost |
|---|---|---|
| What's BTC/ETH/any coin worth right now? | blockrun_price action:"price" category:"crypto" |
FREE |
| Crypto OHLC history | blockrun_price action:"history" category:"crypto" |
FREE |
| FX rate / commodity (gold, oil) | blockrun_price category:"fx" or "commodity" |
FREE |
| Which symbols exist? | blockrun_price action:"list" |
FREE |
| DEX pair, liquidity, volume, contract | blockrun_dex |
FREE |
| Stock quote / history (12 markets) | blockrun_price category:"stocks" |
$0.0020 |
| Token price by contract address | blockrun_defi path:"prices/{coins}" |
$0.0020 |
| Raw JSON-RPC on 40 chains | blockrun_rpc |
$0.0030 |
| Protocol TVL, chain TVL, yields/APY | blockrun_defi |
$0.0060 |
| Everything below (on-chain SQL, wallet labels, social, news, unlocks, liquidations, ETF flows) | blockrun_surf |
$0.0085 |
| Raw SQL over 80+ ClickHouse tables | blockrun_surf path:"onchain/sql" |
$0.0085 |
Every price below is what x402 actually charges (the base plus the gateway's $0.001 flat fee), verified against live payment-required headers — not the base you may see in a 402 body.
The rule: a plain crypto price or a DEX pair is free. Only reach for blockrun_surf when you need something the free tools genuinely do not have — labels, SQL, social, news, unlocks.
Prediction markets are never a Surf question. Surf carries prediction-market/* endpoints, but Predexon (blockrun_markets) serves the same Polymarket/Kalshi data at the same $0.0085 — and adds wallet clustering, smart money, sports, UMA, and five more venues that Surf does not have at all. Price is no longer the argument (it was 7.5× cheaper before 2026-07-15); coverage is, and it is decisive. Route odds, positions and market history to skills/prediction-markets/SKILL.md.
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 · 204 lines · 170 tokens per session scan A fb767159d588
crypto-data is a skill published in the GitHub repository BlockRunAI/blockrun-mcp (393 stars, last pushed today), licensed MIT. It adds 170 tokens to every session and 2,840 once invoked, about $0.0009 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 skills, from other repositories
inventory
Codebase inventory skill — scans the repo for a named pattern (inline SQL, fetch calls, feature flags, debug leftovers, deprecated APIs, etc.) defined by a YAML "recipe pack" and emits a structured Markdown inventory cross-referenced with framework metadata (routes, handlers). The engine is language-agnostic and…
x402-payments
Quote and settle OpenMesha x402 paywalled services (USDC on Base). Use when metering tool calls, outcome fees, or agent-to-agent settlement.
explore
Explore a database schema token-efficiently via the DBHub tools; use before writing SQL against a schema you haven't seen.
adding-personhog-rpc
Guide for adding a new RPC to personhog-replica and personhog-router. Covers eligibility checks, proto definition, code generation for Python and Node.js clients, Rust implementation (storage trait, postgres queries, service handler, router wiring), and index compatibility validation. Use when adding a new gRPC…
query-onchain-data
Query onchain data on Base using the CDP SQL API via x402. Use when you or your user want to view onchain information about decoded blocks, transactions, and events.
create-migration
Create and manage Entity Framework Core database migrations including schema changes, seed data, and rollback strategies. Use when adding or modifying EF Core entities, setting up a new DbContext, applying data seeding, running dotnet ef commands, or troubleshooting migration conflicts.