Borrowing it
Nothing to install: this file belongs to MinaProtocol/mina-mcp-server. 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/MinaProtocol/mina-mcp-server/main/.claude/skills/mesa-upgrade/SKILL.mdgit clone --depth 1 https://github.com/MinaProtocol/mina-mcp-serverWrote 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/minaprotocol/mina-mcp-server/mesa-upgrade)<a href="https://agentmods.dev/skills/minaprotocol/mina-mcp-server/mesa-upgrade"><img src="https://agentmods.dev/badge/skills/minaprotocol/mina-mcp-server/mesa-upgrade/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/skills/minaprotocol/mina-mcp-server/mesa-upgrade"><img src="https://agentmods.dev/badge/skills/minaprotocol/mina-mcp-server/mesa-upgrade.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.00119 | $0.00918 |
| Opus 5 | $0.00060 | $0.00459 |
| Sonnet 5 | $0.00024 | $0.00184 |
| Haiku 4.5 | $0.00012 | $0.00092 |
Grade A, and why
mesa-upgrade 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 9d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mesa upgrade (mesa-mut) runbook
The mesa-mut network is a fork of mainnet state used to rehearse the Mesa
hardfork upgrade. It is a preflight network — it will be reset or retired
without notice; treat all data as ephemeral. This runbook sits on top of the
mina-mcp-server get_upgrade_status tool: that tool is the source of truth for
where in the upgrade we are right now; this file is what to do about it.
Authoritative schedule: https://mesa-upgrade-tracker.minaprotocol.com/status.json.
Always start by calling the tool
Run get_upgrade_status (live mode, --network mesa-mut) before reasoning about
the upgrade or submitting any transaction. Do not infer the phase from wall-clock
time or stale docs — the tool joins the tracker with the live daemon slot, so
its livePhase / transactionsOpen reflect the actual chain, not the schedule.
Key fields:
transactionsOpen— the gate for any send.true→ sends are accepted;false→ sends are dropped, do not submit.currentSlot— live global slot (this chain's genesis).stopTransactionSlot/stopNetworkSlot— thresholds from the tracker.slotsUntilStopTransaction/slotsUntilStopNetwork— remaining headroom.livePhase— the derived phase (below).mesaGenesisTimestamp— when the post-fork chain starts.hints[]— human-readable, already phrased for the current phase.
Phases and what to do
livePhase |
Meaning | Do | Don't |
|---|---|---|---|
pre-upgrade (transactions open) |
currentSlot < stopTransactionSlot |
Normal operation. If submitting a send, confirm slotsUntilStopTransaction leaves comfortable margin (each slot ≈ 3 min). |
Don't start a multi-step flow you can't finish before stopTransactionSlot. |
transactions stopped (awaiting network halt) |
stopTransactionSlot ≤ currentSlot < stopNetworkSlot |
Read-only queries only. Tell the user transactions are frozen until the fork. | Don't submit sends — they are dropped. Don't retry "stuck" transactions. |
network halted (awaiting Mesa genesis) |
currentSlot ≥ stopNetworkSlot |
Wait for mesaGenesisTimestamp. After genesis, treat mesa-mut as a new chain. |
Don't trust pre-fork mempool/tip as current. |
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.
- 9d ago First seen · 64 lines · 119 tokens per session scan A 184a0ac6c85b
mesa-upgrade is a skill published in the GitHub repository MinaProtocol/mina-mcp-server (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 119 tokens to every session and 918 once invoked, about $0.0006 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-31.
Other skills, from other repositories
rustchain-mcp
This skill allows Claude Code to interact with the RustChain blockchain, monitor the network, and hunt for bounties.
chainstack
Work with the Chainstack MCP server to manage blockchain nodes and projects. Use when deploying nodes, migrating to Chainstack from another RPC provider such as QuickNode or Alchemy, checking platform status, searching Chainstack docs, contacting the Chainstack team, or interacting with the Chainstack platform API via…
klever-dev
End-to-end Klever blockchain development — smart contracts (Rust/WASM), transaction building (@klever/connect, klever-go-sdk), deployment via ksc + koperator, and on-chain interaction via MCP tools. Use when the task involves KLV, KDA tokens, klv1 addresses, Klever smart contracts, or Klever node/API interaction.
solana-mcp-skill
This skill teaches AI agents how to interact with the Solana blockchain using the Solana MCP Server.
sui-and-move-tools
Use to get bytecode for a deployed Sui package and produce a disassembled working view. One GraphQL call fetches every module's raw bytecode bytes; sui move disassemble (already on the system, running sui prompt) produces .asm files for analysis. Trigger on "fetch this package's bytecode", "get me the .mv for package…
sora-taira-testnet
Work against the SORA Taira testnet through its deployed Torii MCP endpoint for live account, asset, alias, contract, governance, Musubi package-registry, and transaction workflows. Use when Codex needs to inspect or mutate the Taira testnet, verify or add https://taira.sora.org/v1/mcp, prefer the curated iroha. tool…