Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install debuggingWrote 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/melodic-software/claude-code-plugins/debug)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/debug"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/debug/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/melodic-software/claude-code-plugins/debug"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00195 | $0.06728 |
| Opus 5.5 | $0.00078 | $0.02691 |
| Sonnet 5.5 | $0.00039 | $0.01346 |
| Haiku 4.5 | $0.00019 | $0.00673 |
Grade A, and why
debug scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| 2 | A scripted HTTP call (curl or similar) | the failure shows at an endpoint of a dev server you can start | `curl` the upload endpoint with a 25 MB file and print the status code | How it starts
The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments. [bug description or observation]. e.g., /debugging:debug photo uploads over 20 MB fail with a 502
Repository context. Gather first
Collect these with individual Bash calls, one command per call, never combined into a single invocation:
- Current branch,
git branch --show-current - Recent commits,
git log --oneline -10 - Working tree status (empty = clean),
git status --porcelain | head -10
The pipe is the bound and belongs in the command. A read-time cap ("read only the first 10 entries") bounds nothing: the Bash tool returns the command's complete output into context before there is anything to decide about.
Treat a failure (not a repository, git unavailable) as an unknown value and carry on. Keep these as separate body Bash calls rather than pre-compute lines: the harness runs a skill's whole pre-compute block as one shell invocation, and a worktree-isolated session refuses a compound command that contains git.
Variables
Arguments: $ARGUMENTS
Purpose
This skill turns a reported failure into a command that answers one question, "is the bug still here?", and then uses that command as the judge for every later step. The six phases below each end in a gate. How well Phase 1 goes decides most of the outcome: with a quick, repeatable check that an agent can run unattended, Phases 3 to 5 become routine work; without one, every hypothesis is a guess. The usual way a debugging session goes wrong is starting on causes before any such check exists. Phase 1 and Phase 6 (the check, and the cleanup that removes what the run added) carry the weight; the three phases between them follow from the check.
Scope boundary: this skill starts from an observed failure: UI behaving wrong, a log line that should not appear, a performance regression, a screenshot of a bug, a production symptom. Its first job is to construct a reproduction loop. If the symptom is already a failing test with no reproduction gap, you do not need this skill. Cycle that test directly (reproduce → fix → retest → regression). What /debugging:debug adds over a bare fix loop is a critical edge case: if no correct test seam exists, that absence IS the finding, filed as an architectural recommendation, not a forced test in the wrong place.
What ships with it
7 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.
- 8d ago Changed · +116 lines · +28 tokens per session 36bf14e72f9f
- 9d ago Changed · +1 lines c85997a0cfba
- 15d ago Changed · +6 lines fda43028db3f
- 16d ago Changed · +2 lines 61a9be2b5e02
- 19d ago Changed · -1 lines 6d27ff6e9d17
- 20d ago Changed · +25 lines 9ddda14cec1c
- 21d ago Changed · +1 lines 6d71db376856
- 27d ago Changed · -1 tokens per session b5b7201ab6db
- 1mo ago Changed · +2 lines · -3 tokens per session a17a1c4919d9
- 1mo ago First seen · 193 lines · 171 tokens per session scan A 86ad5228a1cb
debug is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 195 tokens to every session and 6,728 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
benchmark-before-optimize
For performance work: measure before changing, profile to find bottlenecks, compare before and after.
resolve-author-fix
Find the root cause, implement a focused fix, and prove behavior with targeted tests and recordings.
testing
TDD/BDD testing principles. Use when writing tests, reviewing test coverage, setting up testing, or discussing test strategy and test architecture.
agent-test-generator
Specialist subagent: Generates comprehensive test suites using TDD patterns. Use only when the user explicitly asks for tests, improved coverage, or test-first development.
refactor-ops
Safe refactoring patterns - extract, rename, restructure with test-driven methodology and dead code detection. Use for: refactor, refactoring, extract function, extract component, rename, move file, restructure, dead code, unused imports, code smell, duplicate code, long function, god object, feature envy, DRY…
pair-programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…