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 agentmods add skills/bugrabilge/bilge-development-kit/debugnpx skills add bugrabilge/bilge-development-kit --skill debuggit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWhat 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 | $0.00041 | $0.00490 |
| Opus 5 | $0.00020 | $0.00245 |
| Sonnet 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 2d 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.
- 2d 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 4mo ago), licensed MIT. It adds 41 tokens to every session and 490 once invoked, about $0.0002 per session on Opus 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 encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…