Borrowing it
Nothing to install: this file belongs to bugrabilge/bilge-development-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bugrabilge/bilge-development-kit/main/.claude/skills/debug/SKILL.mdgit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/bugrabilge/bilge-development-kit/debug)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/debug"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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/bugrabilge/bilge-development-kit/debug"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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.00041 | $0.00490 |
| Opus 5.5 | $0.00016 | $0.00196 |
| Sonnet 5.5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
debug 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 2mo 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.
What it actually says
/debug - Systematic Problem Investigation
$ARGUMENTS
Purpose
This command activates DEBUG mode for systematic investigation of issues, errors, or unexpected behavior.
Behavior
When /debug is triggered:
-
Gather information
- Error message
- Reproduction steps
- Expected vs actual behavior
- Recent changes
-
Form hypotheses
- List possible causes
- Order by likelihood
-
Investigate systematically
- Test each hypothesis
- Check logs, data flow
- Use elimination method
-
Fix and prevent
- Apply fix
- Explain root cause
- Add prevention measures
Output Format
## 🔍 Debug: [Issue]
### 1. Symptom
[What's happening]
### 2. Information Gathered
- Error: `[error message]`
- File: `[filepath]`
- Line: [line number]
### 3. Hypotheses
1. ❓ [Most likely cause]
2. ❓ [Second possibility]
3. ❓ [Less likely cause]
### 4. Investigation
**Testing hypothesis 1:**
[What I checked] → [Result]
**Testing hypothesis 2:**
[What I checked] → [Result]
### 5. Root Cause
🎯 **[Explanation of why this happened]**
### 6. Fix
```[language]
// Before
[broken code]
// After
[fixed code]
7. Prevention
🛡️ [How to prevent this in the future]
---
## Examples
/debug login not working /debug API returns 500 /debug form doesn't submit /debug data not saving
---
## Key Principles
- **Ask before assuming** - get full error context
- **Test hypotheses** - don't guess randomly
- **Explain why** - not just what to fix
- **Prevent recurrence** - add tests, validation
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.
- 2mo ago First seen · 111 lines · 41 tokens per session scan A aa1100149af0
debug is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 490 once invoked, about $0.0002 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.
Other skills, from other repositories
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.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…