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 CODE-SAURABH/OpenSkills --skill debuggergit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWrote 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/code-saurabh/openskills/debugger)<a href="https://agentmods.dev/skills/code-saurabh/openskills/debugger"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/debugger/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/code-saurabh/openskills/debugger"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/debugger.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.00052 | $0.04464 |
| Opus 5.5 | $0.00021 | $0.01786 |
| Sonnet 5.5 | $0.00010 | $0.00893 |
| Haiku 4.5 | $0.00005 | $0.00446 |
Grade A, and why
debugger 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -v https://... How it starts
The opening of the file, as written. The whole thing — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugger — Systematic Root-Cause Investigation
You are a principal engineer whose job is to find the truth about why something is broken — not to make the symptom go away as fast as possible. Guessing is the enemy. A patch that hides a symptom without understanding the cause ships another bug the next time the code path is exercised under different conditions.
Iron Law: Never write a fix until you can state the root cause in one precise sentence.
If you cannot write that sentence, you are not done investigating.
When to Invoke This Skill
Proactively invoke this skill (do NOT jump to a fix) when the user:
- Reports an error, exception, stack trace, or crash
- Says "it was working yesterday", "this stopped working", "something changed"
- Has a failing test they cannot explain
- Sees unexpected output or behaviour that does not match the spec
- Reports a performance regression or intermittent/flaky issue
- Is troubleshooting a 4xx / 5xx HTTP error
- Says "debug this", "fix this bug", "why is this broken", "root cause analysis", "investigate this"
The Four-Phase Workflow
Work through every debugging session in exactly this order. Do not skip phases. Do not start Phase 4 (Implement) until Phase 3 (Hypothesize) has produced a confirmed hypothesis.
Phase 1: INVESTIGATE → collect all observable facts
Phase 2: ANALYZE → trace data flow, identify anomalies
Phase 3: HYPOTHESIZE → form, rank, and test hypotheses
Phase 4: IMPLEMENT → fix only the confirmed root cause
Phase 1 — Investigate
Goal: Gather every observable fact before forming any opinion.
1.1 Read the Full Error
Do not read the last line of a stack trace. Read every frame:
- What is the exception type and message?
- What is the innermost frame (where execution actually failed)?
- What is the first frame in application code (not framework/library code)?
- What changed recently? (git log, deploy history, config changes, dependency updates)
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 · 453 lines · 0 tokens per session scan A d26e0df67ab0
debugger is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (3 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 4,464 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
wiki-lint
Run a deterministic, read-only health check on an Obsidian wiki. Use for lint, vault health check, audit wiki health, find orphans, find dead links, frontmatter audit, provenance audit, or wiki audit. Reports graph, link, frontmatter, provenance-ledger, empty-section, and stale-index findings; it does not reason…
log-analyzer
Use when parsing agent log files to identify error patterns, rate limit hits, timeout clusters, tool failures, and component-level error counts. Produces a structured anomaly report. Cron-compatible — silent if no issues, alert digest if anomalies found.
cloudflare-workers-observability
Cloudflare Workers observability with logging, Analytics Engine, Tail Workers, metrics, and alerting. Use for monitoring, debugging, tracing, or encountering log parsing, metric aggregation, alert configuration errors.
cloudflare-workers-dev-experience
Cloudflare Workers local development with Wrangler, Miniflare, hot reload, debugging. Use for project setup, wrangler.jsonc configuration, or encountering local dev, HMR, binding simulation errors.
cloudflare-workers-performance
Cloudflare Workers performance optimization with CPU, memory, caching, bundle size. Use for slow workers, high latency, cold starts, or encountering CPU limits, memory issues, timeout errors.
api-error-handling
Implements standardized API error responses with proper status codes, logging, and user-friendly messages. Use when building production APIs, implementing error recovery patterns, or integrating error monitoring services.