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 hautc-it/cil --skill debugginggit clone --depth 1 https://github.com/hautc-it/cilWrote 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/hautc-it/cil/debugging)<a href="https://agentmods.dev/skills/hautc-it/cil/debugging"><img src="https://agentmods.dev/badge/skills/hautc-it/cil/debugging/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/hautc-it/cil/debugging"><img src="https://agentmods.dev/badge/skills/hautc-it/cil/debugging.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.00045 | $0.00308 |
| Opus 5.5 | $0.00018 | $0.00123 |
| Sonnet 5.5 | $0.00009 | $0.00062 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
debugging 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 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.
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
Skill: Debugging
Root cause analysis. Fix causes, not symptoms.
Protocol
- Reproduce — Confirm the bug is reproducible. Get exact error, stack trace, input that triggers it.
- Isolate — Binary search the call stack. Last correct state? First incorrect state?
- Hypothesize — One hypothesis. What single change would cause this behavior?
- Verify — Test hypothesis with minimal reproduction. Add log or assertion to confirm.
- Fix — Fix only the root cause. Don't fix symptoms or add guards around bugs.
- Prevent — Add a test that would have caught this. Document the invariant.
Heuristics
- Recent change? Check git log. Regression = diff caused it.
- Intermittent? Look for race conditions, shared state, external timing.
- Only in prod? Check environment differences: config, data scale, concurrency.
- Works locally? Check dependency versions, build artifacts, env vars.
Anti-patterns
- Adding workarounds without understanding root cause
- Fixing multiple things simultaneously (masks which fix worked)
- Guessing without a reproduction case
- Adding try/catch to hide errors instead of fix them
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 · 32 lines · 45 tokens per session scan A 8c6c81655873
debugging is a skill published in the GitHub repository hautc-it/cil (1 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 308 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
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
log-structured
USE WHEN auditing logging in a legacy codebase, after adopting the JSON-lines spec, or when user asks to clean up logging. Finds print/console.log/interpolated logger calls and suggests spec- compliant replacements per AGENTS.md. Read-only — never auto-rewrites. Templates per language in templates/logging/.
log-correlation
Correlates and troubleshoots logs across OS (Linux/macOS), AWS (CloudWatch, CloudTrail, ALB, Lambda), application (JSON, logfmt), and web servers (Nginx, Apache).
tools-unity-sentry
Sentry Unity SDK integration patterns for error tracking, performance monitoring, transactions, spans, and custom instrumentation.
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.