Kaspa Script Debugger

    1

    Disassemble Kaspa script hex, explain txscript errors, and size compute budgets before you sign. Built for Toccata-era covenants.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Kaspa Script Debugger

    Example session with this skill installed

    My Kaspa transaction got rejected with script units exceeded the amount committed: used 1342, committed 1000. What does that mean and how do I fix it?

    • Read your context and instructions
    • Compiled the kaspa script debugger

    Summary

    I ran the error through explain_script_error. It's a metering limit, not a logic bug: your script ran fine but used more compute than the input paid for.

    What happened

    ExceededCommittedScriptUnits. The script consumed more execution "script units" than the compute budget the input committed to and paid for. Script units are charged for:

    ChargeCost
    Pushed bytes1 per byte
    Hash opcodes1-2 per byte hashed
    ZK proofsfixed
    Sig opsper op

    Here the script used 1342 units against a commitment of 1000.

    How to fix it

    Raise the input's committed compute budget so the allowed script units cover what the script actually uses (at least 1342 here, plus some margin).
    2. Or make the script cheaper: fewer or smaller pushes, a cheaper hash, and don't re-hash large data.

    Next step

    Paste the script hex and I'll run estimate_script_cost to size the budget before you sign again. The estimate covers the dominant charges and isn't the exact consensus value, so commit a little above it.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Writing Kaspa covenants and keep hitting ExceededCommittedScriptUnits or "stack contains N unexpected items"? This skill teaches your agent to use the open-source kaspa-script-mcp server to:

    • turn script hex into opcodes and pushes, the way the engine's parser reads it
    • explain txscript errors in plain language, with a concrete fix
    • estimate script units and compute mass, so you commit the right per-input budget
    • look up any opcode by name or byte

    Offline and deterministic. The opcode table and pricing constants come from rusty-kaspa v2.1.0. Cost figures are estimates, not consensus values, and the skill says so when it matters. It reads scripts only and never signs, broadcasts or touches keys.

    Needs the free MCP server (MIT): https://github.com/DrVelvetFog/kaspa-script-mcp. Setup steps are in the skill.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Web3 & Crypto.

    Cost estimates cover the dominant charges (per-byte, pushed bytes, hash opcodes, fixed ZK costs) and are not the consensus value. ZK per-public-input verifying-key pricing can't be fully derived statically. Opcodes and constants are pinned to rusty-kaspa v2.1.0, so they can go stale after a consensus upgrade. Requires the kaspa-script-mcp server.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    • Free with an Agensi account

    Software
    Kaspa Script MCPGitNode.js 18+

    One-time setup clones the MCP server from GitHub and builds it with npm. After that the tools run offline.

    Permissions

    Terminal / Shell
    Network Access

    Terminal and network are only for the one-time setup (git clone, npm install, npm run build). The four tools run offline, read script hex and error text only, and never sign, broadcast or touch keys.

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Your agent calls deterministic tools whose opcode table and pricing constants are generated from rusty-kaspa v2.1.0, instead of answering from memory. If the server isn't installed, the skill tells the agent to say so rather than guess.

    Node.js 18+, Git, and the free kaspa-script-mcp server (MIT). Clone it from GitHub, run npm install && npm run build, then add it to your agent's MCP config. The skill includes the exact steps.

    It estimates script units and compute mass and gives a minimum per-input budget. That's an estimate of the dominant charges, not the consensus value, so commit some margin above it.

    Toccata-era scripts, pinned to rusty-kaspa v2.1.0 (commit 01b532e). After a consensus upgrade the opcode table and constants may need regenerating.

    No. It reads script hex and error text only. It never signs, broadcasts or handles keys.

    New in Web3 & Crypto

    Free