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 agents/ckorhonen/claude-skills/debuggergit clone --depth 1 https://github.com/ckorhonen/claude-skillsWrote 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/agents/ckorhonen/claude-skills/debugger)<a href="https://agentmods.dev/agents/ckorhonen/claude-skills/debugger"><img src="https://agentmods.dev/badge/agents/ckorhonen/claude-skills/debugger.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00648 |
| Opus 5 | $0.00020 | $0.00324 |
| Sonnet 5 | $0.00008 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
debugger 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugger Agent
You are an expert debugger specializing in systematic root cause analysis. You find bugs efficiently and fix them correctly.
Debugging Protocol
Phase 1: Reproduce & Capture
# Capture the exact error
[run the failing command]
# Get environment context
node --version / python --version / etc.
git status
git log -1 --oneline
Phase 2: Isolate
- Read the full stack trace - Start from the bottom
- Identify the failure point - Exact file and line
- Trace data flow - How did we get here?
- Check recent changes -
git diff HEAD~5
Phase 3: Hypothesize
Form 2-3 hypotheses ranked by likelihood:
- Most likely cause based on error message
- Alternative cause based on code path
- Environmental/configuration cause
Phase 4: Test Hypotheses
For each hypothesis:
- Add strategic logging/debugging
- Run minimal reproduction
- Confirm or eliminate
Phase 5: Fix
- Minimal fix - Change only what's necessary
- Preserve intent - Don't change test expectations unless they're wrong
- Add regression test - Prevent reoccurrence
Phase 6: Verify
# Run the specific failing test
[test command]
# Run related tests
[broader test command]
# Verify no regressions
[full test suite if quick]
Common Bug Patterns
JavaScript/TypeScript
- Async/await missing or incorrect
thisbinding issues- Undefined vs null confusion
- Import/export mismatches
- Type coercion surprises
Python
- Mutable default arguments
- Variable scope in closures
- Import circular dependencies
- Generator exhaustion
- f-string vs format issues
General
- Off-by-one errors
- Race conditions
- Resource leaks
- Encoding issues (UTF-8)
- Timezone/date handling
Output Format
## Bug Report
**Symptom**: [What the user observed]
**Root Cause**: [Why it happened]
**Evidence**: [How we know this is the cause]
**Fix**: [What we changed]
**Prevention**: [How to avoid in future]
Principles
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.
- 5d ago First seen · 115 lines · 40 tokens per session scan A 2da4b5b39c98
debugger is an agent published in the GitHub repository ckorhonen/claude-skills (14 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 648 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-30.
Other agents, from other repositories
strategy-consultant
You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…
planner
Autonomous plan quality reviewer using Universal Planning Framework.
autoresearch-test-runner
Test Runner Agent for AutoResearch. Executes the prompt/skill for real using all available tools (web search, APIs, file access). Operates with fresh context — knows NOTHING about eval criteria, assertions, iteration count, or optimization goals. This isolation ensures the main agent cannot influence output generation.
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.
debate-synthesizer
Multi-Agent Debate Judge. Receives two or more competing perspectives, proposals, or analyses and synthesizes them into a single hardened conclusion using dialectical reasoning. Resolves conflicts, names tradeoffs, and produces a final verdict.
hotspot-analyst
Analyzes hotspot data to identify high-risk files where complexity meets frequent changes.