Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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-upgrade)<a href="https://agentmods.dev/skills/blockrunai/blockrun-mcp/blockrun-upgrade"><img src="https://agentmods.dev/badge/skills/blockrunai/blockrun-mcp/blockrun-upgrade.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.00071 | $0.01742 |
| Opus 5 | $0.00036 | $0.00871 |
| Sonnet 5 | $0.00014 | $0.00348 |
| Haiku 4.5 | $0.00007 | $0.00174 |
Grade D, and why
blockrun-upgrade scanned grade D with 2 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 6d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls .claude/skills ~/.claude/skills 2>/dev/null # where were they copied? Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.npm/_npx # safe — it is only a download cache How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrading BlockRun MCP
The server is run by npx, so "upgrading" means making npx fetch a newer version and
the client restart into it. Which of those two is the problem depends on how it was
installed.
1. Read how it was installed
claude mcp get blockrun # registered command + args + env + scope
npm view @blockrun/mcp version # what "latest" is on the registry right now
| Registered spec | What happens at each client start |
|---|---|
npx -y @blockrun/mcp@latest |
npx re-resolves latest against the registry and downloads if newer. A client restart is the upgrade. |
npx -y @blockrun/mcp (no tag) |
npx reuses whatever is in ~/.npm/_npx — the version from the day it was installed. Restarting changes nothing. |
npx -y @blockrun/[email protected] |
Pinned on purpose. Only changes if you re-register. |
The startup notice is the server telling you it is not on latest:
[BlockRun] Update available: v0.39.2 → v0.42.0
[BlockRun] Run: claude mcp add blockrun -s user -- npx -y @blockrun/mcp@latest
2. Upgrade
Registered with @latest: restart the client. Done. If the notice persists, the cache
is stale or the registry was unreachable at start:
rm -rf ~/.npm/_npx # safe — it is only a download cache
then restart again.
Registered without a tag, or pinned: re-register with @latest. claude mcp add
refuses a name that already exists, so remove first — at the scope claude mcp get
reported — and carry every env var and flag it printed across, one -e each, flags
after the package:
claude mcp remove blockrun -s user
claude mcp add blockrun -s user \
-e PATH="$PATH" -e BLOCKRUN_KEYCHAIN=auto -e BLOCKRUN_CONFIRM_SPEND=on \
-- npx -y @blockrun/mcp@latest --profile trading
Codex: codex mcp remove blockrun then codex mcp add blockrun -- npx -y @blockrun/mcp@latest.
JSON clients (Claude Desktop / Cursor / Windsurf): edit args to ["-y", "@blockrun/mcp@latest"].
Then quit and relaunch the client (Claude Code: /mcp reconnect blockrun respawns just
this server). A running session keeps the old process until you do.
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.
- 6d ago First seen · 142 lines · 71 tokens per session scan D fd8fe7bcdd42
blockrun-upgrade is a skill published in the GitHub repository BlockRunAI/blockrun-mcp (393 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,742 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 2 findings (enumerates other installed skills, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
resolve-pr-comments-stack
Resolve unresolved PR review comments across an entire Graphite (gt) stack of many PRs, bottom-up, in one working directory. Use when asked to "go through this stack and resolve comments", "clean up review comments across the whole stack", or given a list/range of PR numbers that form (or partially form) a gt stack.…
resolve-pr-comments
Skill "resolve-pr-comments" from maximhq/bifrost, covering resolve pr comments, usage, workflow overview, step 1: detect repository and step 2: fetch unresolved comments (graphql).
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].
portainer-mcp-hygiene
How to drive the Portainer MCP server's tools correctly — both reading and mutating. Reading: project responses with select (JMESPath), where the heavy fields live (snapshots, status blocks, managed fields), how to handle non-JSON Docker/K8s proxy endpoints (container and pod logs, stats, exec), and how to interpret…
vault-for-llm
Connect OpenClaw to Vault Agent Memory as a local-first governed project memory layer. Search first, then bounded-read cited source ranges; propose new memories as candidates instead of writing directly into active memory.
setup
Configure the Qdrant Power after installation. Use this skill for missing uvx, missing environment variables, unapproved environment variables, unavailable Qdrant tools, "Failed to connect" errors, and setup requests.