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.
npx skills add AlmogBaku/debug-skill --skill debugging-codegit clone --depth 1 https://github.com/AlmogBaku/debug-skillWrote 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.
[](https://agentmods.dev/skills/almogbaku/debug-skill/debugging-code)<a href="https://agentmods.dev/skills/almogbaku/debug-skill/debugging-code"><img src="https://agentmods.dev/badge/skills/almogbaku/debug-skill/debugging-code/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.
<a href="https://agentmods.dev/skills/almogbaku/debug-skill/debugging-code"><img src="https://agentmods.dev/badge/skills/almogbaku/debug-skill/debugging-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk warn
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.1 | $0.00079 | $0.02652 |
| Opus 5.5 | $0.00032 | $0.01061 |
| Sonnet 5.5 | $0.00016 | $0.00530 |
| Haiku 4.5 | $0.00008 | $0.00265 |
Grade A, and why
debugging-code 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- debugging-code — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive Debugger
Use when a program crashes, produces wrong output, or you need to understand exactly how execution reached a particular state — and running it again with more print statements won't give you the answer fast enough.
You can pause a running program at any point, read live variable values and the call stack at that exact moment, step forward line by line or jump to the next breakpoint, and evaluate arbitrary expressions against the live process — all without restarting.
Setup
This skill uses dap, a CLI tool that background daemon to interact with the debugger via the DAP Protocol, maintain
the debugger state, so you can simply interact with it with multiple calls.
If dap isn't installed (check: command -v dap), install it NOW.
Ask/notify the user before proceeding to install it.
From Homebrew (macOS)
brew install AlmogBaku/tap/dap
Installer script:
bash scripts/install-dap.sh
Install from sources:
go install github.com/AlmogBaku/debug-skill/cmd/dap@latest
This tool is open-sourced and available on GitHub, maintained and follows best practices.
Supports natively Python, Go, Node.js/TypeScript, Rust, C/C++, and any other language that supports DAP.
If a debugger backend is missing or fails to start, see references/installing-debuggers.md
For all commands and flags: dap --help or dap <cmd> --help.
Starting a Session
dap debug <file> launches the program under the debugger. Backend is auto-detected from the file extension.
Choose your starting strategy based on what you know:
- Have a hypothesis — set a breakpoint where you expect the bug:
dap debug script.py --break script.py:42 - Conditional breakpoint — only stop when a condition is met:
dap debug script.py --break "script.py:42:x > 5"( always quote specs with conditions) - Multi-file app — breakpoints across modules:
--break src/api/routes.py:55 --break src/models/user.py:30 - No hypothesis, small program — walk from entry:
dap debug script.py --stop-on-entry(avoid for large projects — startup code is noisy; bisect with breakpoints instead) - Exception, location unknown —
dap debug script.py --break-on-exception raised(Python) /all(Go/JS) - Remote process —
dap debug --attach host:port --backend <name> - Process already running (stuck server, live issue) — attach without restarting:
dap debug --pid <PID> --backend <name>macOS + Go gotcha:
dlv --pidrequires SIP disabled (csrutil disable). Prefer starting the program under the debugger instead or attaching to a remote debugger!
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 268 lines · 79 tokens per session scan A cb00d6834230
debugging-code is a skill published in the GitHub repository AlmogBaku/debug-skill (335 stars, last pushed 6mo ago), licensed MIT. It adds 79 tokens to every session and 2,652 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.