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/blockrunnpx skills add BlockRunAI/blockrun-mcp --skill blockrungit 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)<a href="https://agentmods.dev/skills/blockrunai/blockrun-mcp/blockrun"><img src="https://agentmods.dev/badge/skills/blockrunai/blockrun-mcp/blockrun.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.00246 | $0.02633 |
| Opus 5 | $0.00123 | $0.01316 |
| Sonnet 5 | $0.00049 | $0.00527 |
| Haiku 4.5 | $0.00025 | $0.00263 |
Grade A, and why
blockrun 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 4d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BlockRun
One wallet, pay-per-call, no API keys. Every paid tool below settles in USDC over x402 at the moment of the call.
Never quote a price from memory
There is no price table in this skill, and that is deliberate. Every flat per-call price published in this repo drifted by exactly the per-transaction fee the last time that fee changed, because each one was a typed copy. Read prices from a live source instead:
| Need | Where |
|---|---|
| Per-token model pricing | blockrun_models |
| What a call will actually cost | the 402 response — it carries the real amount |
| Full endpoint catalog with prices | https://blockrun.ai/llms.txt (Base) · https://sol.blockrun.ai/llms.txt (Solana) |
The tool descriptions in the MCP server carry current prices too; they are generated, not typed.
The two chains are not the same gateway
blockrun.ai and sol.blockrun.ai are separate deployments, and
blockrun_wallet action: "chain" switches between them mid-session. Two consequences,
both easy to miss because nothing announces the switch:
Prices differ, on purpose. Every figure in these skills is the Base price. Base
adds a flat per-transaction fee; Solana deliberately adds none — the ~$0.001-per-call gap
is pricing policy (an incentive to settle on Solana), not drift, so do not expect it to be
"fixed". Each gateway's own llms.txt quotes its own convention — read the one for the
chain you are on, or just read the 402.
Some tools do not exist on Solana at all. Verified against both gateways 2026-08-07:
| Tool | On Solana | What you get |
|---|---|---|
blockrun_defi |
✗ not served | 404 — reads like a bad path, but the path is fine |
blockrun_modal |
✗ not served | 503 on all four sandbox actions — reads like an outage |
| everything else | ✓ | ~$0.001 cheaper than the figure printed here |
Both tools now refuse before the round trip and tell you to switch, so you should never
see the raw 404/503 through the MCP. If you are calling the HTTP API directly you
will, and neither status says "wrong chain" — check the chain first.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 184 lines · 246 tokens per session scan A f999d97fc8c5
blockrun is a skill published in the GitHub repository BlockRunAI/blockrun-mcp (393 stars, last pushed yesterday), licensed MIT. It adds 246 tokens to every session and 2,633 once invoked, about $0.0012 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
research-article-analysis
Systematically validate a research article's claims against TogoMCP RDF databases — molecular formulas, reaction equations, pathways, protein function, GO definitions — instead of trusting the paper's text or keyword-search snippets. Use whenever the user asks to "analyze this paper/article", fact-check or validate a…
x402-payments
Quote and settle OpenMesha x402 paywalled services (USDC on Base). Use when metering tool calls, outcome fees, or agent-to-agent settlement.
onesource-report-bug
Report a bug or unexpected error in OneSource MCP to the OneSource team using the 1sreportbug tool. Use when a 1s blockchain tool returns an unexpected error, or when the user explicitly asks to report a problem. Free, no payment required. Do NOT report 402 (payment/auth) or 403 (subscription) responses — those are…
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
review-pr
Reviews a PR or diff with multi-angle finders and adversarial verification, then reports a findings table, a merge/no-merge recommendation, required followups, and offers to create a follow-up PR. Use when the user types /review-pr [PR# | branch | path].