Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Node Debug Inspector

    10

    Attach to a Node.js process through the V8 inspector protocol and drive breakpoints, stack walks, and variable dumps with zero extra dependencies. Use when a No

    Free

    6 usesSecurity scanned
    Node Debug Inspector

    Node Debug Inspector

    Example session with this skill installed

    Attach to the process at 127.0.0.1:9333, set a breakpoint at line 41 of src/server.js, and dump the value of the 'config' object when hit.

    • Read your context and instructions
    • Compiled the node debug inspector

    Target attached. Breakpoint set at src/server.js:41. Pause event received. **Evaluation result for 'config':** { port: 8080, db: 'active', retries: 3 }. Resuming process.

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

    About this skill

    The problem

    Print debugging fails when issues involve deep closures, unhandled promise rejections, or complex state that console.log cannot reach. Setting up a full IDE debugger often introduces too much friction or environment overhead for a quick probe.

    What it does

    • Attaches to running Node.js processes via the V8 Chrome DevTools Protocol (CDP).
    • Sets targeted breakpoints and conditional pauses without modifying source code.
    • Evaluates expressions directly within the local scope of a paused call frame.
    • Generates CPU profiles to identify performance bottlenecks in hot endpoints.
    • Walks call stacks to trace the origin of errors or hanging requests.

    Frameworks & tools

    Node.js (v22+ for native WebSocket support), Chrome DevTools Protocol (CDP), and curl.

    Why this beats prompting it yourself

    Manually constructing CDP JSON-RPC messages is error-prone and requires deep knowledge of the V8 inspector's internal methods. This skill automates the boilerplate for WebSocket handshakes and frame evaluation, providing immediate access to the process internals without manual protocol implementation.

    Use cases

    • Debug a hanging request by inspecting the state of unresolved promises.
    • Recover variable values from private closures during a production-like crash.
    • Verify execution paths in complex test suites without adding instrumentation.
    • Capture CPU profiles of specific functions to resolve latency spikes.

    Known limitations

    Requires the Node.js process to be started with the --inspect flag or triggered via SIGUSR1. Native WebSocket support requires Node.js 22 or higher for the probe script.

    Requires Node.js 22+ for the native global WebSocket in the probe script. The target process must be accessible via a TCP port. Restricted to Node.js environments.

    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 any payment.

    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

    6 uses

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    • Free with an Agensi account

    Requires

    Node.js

    Permissions

    Terminal / Shell
    Network Access
    Listed3 months ago

    What's inside

    Frequently Asked Questions

    This skill enables an AI agent to interface directly with the V8 Chrome DevTools Protocol, allowing it to set breakpoints, inspect variables, and walk call stacks in a live Node.js process without manual console.log instrumentation.

    The target Node.js process must be started with the `--inspect` flag (or triggered via SIGUSR1), and the environment running the probe requires Node.js v22 or higher to leverage native WebSocket support.

    No, this skill is designed to attach to running processes using the V8 inspector protocol, meaning you can debug and evaluate state without modifying your source code or restarting the application.

    You receive the complete skill definition, including the logic for WebSocket handshakes and JSON-RPC message construction, along with documentation on how to integrate it with your AI agent.

    While the skill provides the interface to inspect and evaluate code, it cannot bypass OS-level firewall restrictions; the AI agent must have network access to the debugging port (default 9229) of the target process.

    New in Testing & Debugging