What is node-debugging?

A guide for debugging Node.js backend programs, including API servers, workers, and scripts. It uses tracepoints, logpoints, exceptionpoints, and JavaScript evaluation while the process runs.

Use it to connect to a Node process by PID, name, container, or inspector address, then trace calls, inspect variables, monitor exceptions, or run JavaScript.

It helps inspect a live Node.js process without stopping it or adding temporary logging throughout the code. This can make server-side errors and state easier to trace.

node-debugging — Skill by serkan-ozal

Install

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.

agentmods

npx agentmods add skills/serkan-ozal/browser-devtools-claude/node-debugging

Any agent

npx skills add serkan-ozal/browser-devtools-claude --skill node-debugging

Clone the repo

git clone --depth 1 https://github.com/serkan-ozal/browser-devtools-claude

Made for: Claude Code, Codex.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 725 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00039	$0.00725
Opus 5	$0.00019	$0.00362
Sonnet 5	$0.00008	$0.00145
Haiku 4.5	$0.00004	$0.00072

Measured 2d ago against content hash 27e09799e101, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

node-debugging 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 2d 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.

skills/node-debugging/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Node.js Backend Debugging Skill

Debug Node.js backend processes using non-blocking tracepoints, logpoints, exceptionpoints, and JavaScript execution. Use when the user needs to debug API servers, workers, or backend scripts.

When to Use

This skill activates when:

User asks to debug Node.js backend or API
User wants to trace function calls in a running server
User needs to inspect variables or state in a Node process
User mentions backend errors, API bugs, or server-side issues
User wants to run JavaScript in a connected Node process

Prerequisites

Use MCP with PLATFORM=node or run node-devtools-mcp separately
Connect to the target process before other debug commands (debug_connect)

Capabilities

Connection

Connect by PID (debug_connect with pid)
Connect by process name (debug_connect with processName)
Connect by Docker container (debug_connect with containerName or containerId)
Connect by inspector port or WebSocket URL

For Docker: use host.docker.internal or container name when MCP runs in a container. Mount /var/run/docker.sock in the MCP container.

Non-Blocking Debugging

Tracepoints (debug_put-tracepoint): Capture call stack and local variables at code locations
Logpoints (debug_put-logpoint): Evaluate and log expressions
Exceptionpoints (debug_put-exceptionpoint): Capture on uncaught or all exceptions
Watch expressions (debug_add-watch): Evaluate at every tracepoint hit

Snapshot Retrieval

debug_get-probe-snapshots (types: tracepoint, logpoint, exceptionpoint; returns tracepointSnapshots, logpointSnapshots, exceptionpointSnapshots)
debug_clear-probe-snapshots — clear when done to free memory

Console & Source Maps

Console logs (debug_get-logs): Captures console.log, error, warn from the Node process
Source maps (debug_resolve-source-location): Resolve bundled code to original source

JavaScript Execution

Use execute on the Node platform for batch tool calls (callTool only; no page). See commands/node/execute.md.

Read the full file on GitHub · 67 lines

Changes

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.

2d ago First seen · 67 lines · 39 tokens per session scan A 27e09799e101

Subscribe to this mod's changes

node-debugging is a skill published in the GitHub repository serkan-ozal/browser-devtools-claude (8 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 725 once invoked, about $0.0002 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.

Backend and APIs Debugging Languages

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens