Prismer Node Inspect Debugger

What it does

When your agent uses it

• Tasks that involve Browser testing

Example prompts

• “/prismer-node-inspect-debugger”

Requirements

• Python 3
• Node.js

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1Wrong line numbers in TS source. Breakpoints hit the emitted JS, not the .ts. Either (a) break in the built dist/*.js, or (b) enable…
2. 2inspect vs --inspect-brk. --inspect starts the inspector but doesn't pause; your script races past your first breakpoint if you attach too…
3. 3Port collisions. Use --inspect=127.0.0.1:0 and read the actual WebSocket
4. 4Child processes. Allocate a distinct/random loopback port to each child.
5. 5Background kills. If you Ctrl+C out of node inspect while the target is paused, the target stays paused. Either cont first, or kill the…
6. 6Running node inspect through an agent terminal. It's a PTY-friendly REPL. In Hermes, launch it with terminal(pty=true) or background=true…
7. 7Security. Public inspector bindings expose arbitrary code execution. Always bind to 127.0.0.1 (the default) unless you have an isolated…

What it can do on your machine

Read from SKILL.md and the folder at commit e5d9444. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • node
  • npm
  • curl
  • jq

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use npm and curl, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prismer Node Inspect Debugger loads about 3k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 949 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~22

When it runs · the whole SKILL.md, loaded when a task matches

~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Prismer-AI/PrismerCloud at commit e5d9444, republished under its MIT licence (© Prismer-AI). 949 words, ~3,046 tokens.

name

prismer-node-inspect-debugger

description

Debug Node.js via --inspect + Chrome DevTools Protocol CLI.

scope

coding

version

1.0.0

author

Hermes Agent

license

MIT

platforms

linux, macos, windows

metadata.nativeReplaces

node-inspect-debugger

metadata.requiresExplicitGrant

true

node inspect path/to/script.js
# or with tsx
node --inspect-brk $(which tsx) path/to/script.ts

# 1. Send SIGUSR1 to enable the inspector on an existing process
kill -SIGUSR1 <pid>
# Node prints: Debugger listening on ws://127.0.0.1:9229/<uuid>

# 2. Attach the debugger CLI
node inspect -p <pid>
# or by URL
node inspect ws://127.0.0.1:9229/<uuid>

node --inspect script.js           # listen on 127.0.0.1:9229, keep running
node --inspect-brk script.js       # listen AND pause on first line
node --inspect=0.0.0.0:9230 script.js   # custom host:port

node --inspect-brk --import tsx script.ts
# or older tsx
node --inspect-brk -r tsx/cjs script.ts

npm i -g chrome-remote-interface        # or project-local
# Start your target:
node --inspect-brk=9229 target.js &

const CDP = require('chrome-remote-interface');

(async () => {
  const client = await CDP({ port: 9229 });
  const { Debugger, Runtime } = client;

  Debugger.paused(async ({ callFrames, reason }) => {
    const top = callFrames[0];
    console.log(`PAUSED: ${reason} @ ${top.url}:${top.location.lineNumber + 1}`);

    // Walk scopes for locals
    for (const scope of top.scopeChain) {
      if (scope.type === 'local' || scope.type === 'closure') {
        const { result } = await Runtime.getProperties({
          objectId: scope.object.objectId,
          ownProperties: true,
        });
        for (const p of result) {
          // Only inspect pre-approved non-sensitive fields, never every local.
          if (['status', 'phase'].includes(p.name)) {
            console.log(`  ${scope.type}.${p.name} =`, p.value?.value);
          }
        }
      }
    }

    // Evaluate an expression in the paused frame
    const { result } = await Debugger.evaluateOnCallFrame({
      callFrameId: top.callFrameId,
      expression: 'typeof state',
    });
    console.log('state =', result.value ?? result.description);

    await Debugger.resume();
  });

  await Runtime.enable();
  await Debugger.enable();

  // Set a breakpoint by URL regex + line
  await Debugger.setBreakpointByUrl({
    urlRegex: '.*app\\.tsx$',
    lineNumber: 119,       // 0-indexed
    columnNumber: 0,
  });

  await Runtime.runIfWaitingForDebugger();
})();

node ~/.hermes/cache/scratch/cdp-debug.js

mkdir -p ~/.hermes/cache/scratch/cdp-tools && cd ~/.hermes/cache/scratch/cdp-tools && npm i chrome-remote-interface
NODE_PATH=~/.hermes/cache/scratch/cdp-tools/node_modules node ~/.hermes/cache/scratch/cdp-debug.js

cd <hermes-agent-repo>/ui-tui
npm run build    # produce dist/ once so transpile isn't needed on first load
node --inspect-brk dist/entry.js
# In another terminal:
node inspect -p <node pid>

sb('dist/app.js', 220)     # or wherever the suspect render is
cont

# 1. Launch TUI
hermes --tui &
TUI_PID=$(pgrep -f 'ui-tui/dist/entry' | head -1)

# 2. Enable inspector on that Node PID
kill -SIGUSR1 "$TUI_PID"

# 3. Find the WS URL
curl -s http://127.0.0.1:9229/json/list | jq -r '.[0].webSocketDebuggerUrl'

# 4. Attach
node inspect ws://127.0.0.1:9229/<uuid>

cd <hermes-agent-repo>/ui-tui
# Run a single test file paused on entry
node --inspect-brk ./node_modules/vitest/vitest.mjs run --no-file-parallelism src/app/foo.test.tsx

// CPU profile for 5 seconds
await client.Profiler.enable();
await client.Profiler.start();
await new Promise(r => setTimeout(r, 5000));
const { profile } = await client.Profiler.stop();
const fs = require('node:fs');
const path = require('node:path');
const os = require('node:os');
const out = fs.mkdtempSync(path.join(os.tmpdir(), 'prismer-profile-'));
fs.writeFileSync(path.join(out, 'cpu.cpuprofile'), JSON.stringify(profile), {flag: 'wx', mode: 0o600});
console.log(out);
// Attach the returned task-owned profile path; it may contain sensitive data.

// Heap snapshot
await client.HeapProfiler.enable();
const chunks = [];
client.HeapProfiler.addHeapSnapshotChunk(({ chunk }) => chunks.push(chunk));
await client.HeapProfiler.takeHeapSnapshot({ reportProgress: false });
const fs = require('node:fs');
const path = require('node:path');
const out = fs.mkdtempSync(path.join(require('node:os').tmpdir(), 'prismer-heap-'));
fs.writeFileSync(path.join(out, 'heap.heapsnapshot'), chunks.join(''), {flag: 'wx', mode: 0o600});
console.log(out);

node --inspect-brk script.js &
node inspect -p $!
# debug>
sb('script.js', X)
cont
# paused. Now:
repl
> myVariable
> Object.keys(this)

debug> sb('suspectFn')
debug> cont
# paused on entry
debug> bt

# Start with --inspect (no -brk), let it run to the hang, then:
debug> pause
debug> bt
# Now you see the stuck frame

© Prismer-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in sdk/cloud/catalog/skills/prismer-node-inspect-debugger of Prismer-AI/PrismerCloud.

• SKILL.md
• LICENSE
• NOTICE.md

Open the folder on GitHubat commit e5d9444

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in Prismer-AI/PrismerCloud, which our catalogue first saw on October 7, 2026.

• mateaix/mateclawmateclaw-server/src/main/resources/skills/node-inspect-debugger
• NousResearch/hermes-agentskills/software-development/node-inspect-debugger
• johnson7788/MultiUserClawhermes-agent/skills/software-development/node-inspect-debugger