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/kreek/consult/debuggingnpx skills add kreek/consult --skill debugginggit clone --depth 1 https://github.com/kreek/consultWhat 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.00020 | $0.00852 |
| Opus 5 | $0.00010 | $0.00426 |
| Sonnet 5 | $0.00004 | $0.00170 |
| Haiku 4.5 | $0.00002 | $0.00085 |
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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging
Iron Law
NO FIX WITHOUT ROOT-CAUSE EVIDENCE.
When to Use
- Investigating defects, flakes, timing-sensitive bugs, regressions, production incidents, unclear failures, or "stuck" debugging sessions.
When NOT to Use
- Planned refactors with no failing behavior; use
refactoring. - Performance investigation where the symptom is slowness; use
performance. - Git-history regression search mechanics; pair with
git-workflow.
Core Ideas
- Reproduce before fixing. Change one variable per experiment.
- Reduce the failing case until only the bug remains. Localize by boundary: data, service, integration, application, infrastructure.
- Debugging should improve the human's failure model with evidence.
- Fix causes, not symptoms.
- For incidents, produce blameless learning with owned follow-up actions, never "human error" as a root cause.
Workflow
- Capture the exact symptom: command, input, output, stack trace, timing, environment. Reproduce reliably or record why reproduction isn't yet possible.
- After the third experiment, keep a short debug log. Form one hypothesis at a time, predict what else must be true, run the smallest experiment that confirms or refutes it.
- Before editing, state the current failure model: likely cause, evidence for it, and the observation that would disprove it.
- Fix the identified cause. Add a regression test or operational guard before declaring fixed.
Verification
- The bug reproduces on pre-fix code or non-reproducibility is documented.
- The root cause is named in one sentence, explains all observed symptoms, and identifies evidence that ruled out main alternatives.
- The fix is one atomic change aimed at that cause, with a regression test or equivalent guard that fails before and passes after.
- Timing-sensitive bugs were verified with non-invasive observation or replay.
- Incident follow-ups have owners and deadlines.
- Unproven root-cause or fix claims are reported as unproven.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 82 lines · 20 tokens per session scan A e7fb12f9d4c8
debugging is a skill published in the GitHub repository kreek/consult (1 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 852 once invoked, about $0.0001 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
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.