debugging

debugging is a skill for Claude Code from ironbee-ai/ironbee-devtools-skills. It costs 74 tokens per session (2,426 once invoked), scanned A, original, MIT.

A debugging guide for web apps, Node.js backends, and running Python programs. It uses console messages, network requests, logs, tracepoints, and exception monitoring to help find problems.

In plain words
What is it for?
Use it to inspect browser errors, API calls, page loading, JavaScript function calls, and Python issues such as stuck threads or lockups.
Why use it?
It reduces the need to guess where a bug is by showing what the application and its network connections are doing. It also supports investigating problems without pausing the program at breakpoints.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to inspect browser errors, API calls, page loading, JavaScript function calls, and Python issues such as stuck threads or lockups.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ironbee-ai/ironbee-devtools-skills/debugging
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.

Any agent
npx skills add ironbee-ai/ironbee-devtools-skills --skill debugging
Clone the repo
git clone --depth 1 https://github.com/ironbee-ai/ironbee-devtools-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/ironbee-ai/ironbee-devtools-skills/debugging/github.svg)](https://agentmods.dev/skills/ironbee-ai/ironbee-devtools-skills/debugging)
Your own site
<a href="https://agentmods.dev/skills/ironbee-ai/ironbee-devtools-skills/debugging"><img src="https://agentmods.dev/badge/skills/ironbee-ai/ironbee-devtools-skills/debugging/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.

agentmods 80×15 button for debugging

Your own site · 80×15
<a href="https://agentmods.dev/skills/ironbee-ai/ironbee-devtools-skills/debugging"><img src="https://agentmods.dev/badge/skills/ironbee-ai/ironbee-devtools-skills/debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,426 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.02426
Opus 5.5 $0.00030 $0.00970
Sonnet 5.5 $0.00015 $0.00485
Haiku 4.5 $0.00007 $0.00243

Measured 1mo ago against content hash f8b824770dd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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/debugging/SKILL.md · 234 lines

How it starts

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

Debugging Skill

Debug web applications, Node.js backends, and running Python processes using console inspection, network analysis, and non-blocking code debugging with tracepoints, logpoints, and exception monitoring.

When to Use

This skill activates when:

  • User reports a bug or error on a web page or backend
  • User asks to debug JavaScript (frontend or Node.js) or Python (a running process)
  • User wants to inspect API calls or network requests
  • User needs to troubleshoot page loading or API handler issues
  • User mentions console errors or warnings
  • User wants to debug without breakpoints
  • User needs to trace function calls or monitor variables
  • User needs to diagnose a Python deadlock, GIL contention, or hung threads

Capabilities

Console Inspection

ironbee-browser-devtools-cli o11y get-console-messages
ironbee-browser-devtools-cli o11y get-console-messages --type warning
ironbee-browser-devtools-cli --json o11y get-console-messages --type error

Network Analysis

ironbee-browser-devtools-cli o11y get-http-requests
ironbee-browser-devtools-cli --json o11y get-http-requests --resource-type fetch
ironbee-browser-devtools-cli --json o11y get-http-requests --status '{"min":400}'

Tracepoints (Non-Blocking)

ironbee-browser-devtools-cli debug put-tracepoint --url-pattern "app.js" --line-number 42
ironbee-browser-devtools-cli debug list-probes --types tracepoint
ironbee-browser-devtools-cli debug remove-probe --type tracepoint --id <probe-id>
ironbee-browser-devtools-cli debug clear-probes --types tracepoint

Logpoints

ironbee-browser-devtools-cli debug put-logpoint --url-pattern "app.js" --line-number 50 --log-expression "user.id"
ironbee-browser-devtools-cli debug list-probes --types logpoint
ironbee-browser-devtools-cli debug remove-probe --type logpoint --id <probe-id>
ironbee-browser-devtools-cli debug clear-probes --types logpoint

Exception Monitoring

ironbee-browser-devtools-cli debug put-exceptionpoint --state uncaught
ironbee-browser-devtools-cli debug put-exceptionpoint --state all

Read the full file on GitHub · 234 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.

  1. 1mo ago First seen · 234 lines · 74 tokens per session scan A f8b824770dd1

Subscribe to this mod's changes

debugging is a skill published in the GitHub repository ironbee-ai/ironbee-devtools-skills (3 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 2,426 once invoked, about $0.0003 per session on Opus 5.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.

Related

Other skills, from other repositories

react-sentinel-debug

Use React-Sentinel when a task needs live browser or React runtime inspection rather than static code reading alone.

edgarbnt/ReactSentinel · 26 tokens

moli-webfetch

Fetch, inspect, crawl, and capture live, JavaScript-rendered websites with Moli. Use when Codex needs current web content, web research, fact lookup, link following, a bounded crawl, client-rendered or response-gated content, network diagnostics, or a standalone HTML, Markdown, JSON, semantic-tree, viewport or…

lexmount/moli · 90 tokens

kiro-verify-completion

Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.

gotalab/cc-sdd · 39 tokens

diagnose-backend-bug

Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…

QoderAI/better-harness · 87 tokens

prismer-python-debugpy

Debug Python: pdb REPL + debugpy remote (DAP).

Prismer-AI/PrismerCloud · 19 tokens

debug-live

Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…

microsoft/DebugMCP · 84 tokens