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 jstoup111/ai-conductor --skill debugginggit clone --depth 1 https://github.com/jstoup111/ai-conductorWrote 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/jstoup111/ai-conductor/debugging)<a href="https://agentmods.dev/skills/jstoup111/ai-conductor/debugging"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/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/jstoup111/ai-conductor/debugging"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/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.00048 | $0.01608 |
| Opus 5.5 | $0.00019 | $0.00643 |
| Sonnet 5.5 | $0.00010 | $0.00322 |
| Haiku 4.5 | $0.00005 | $0.00161 |
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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Prevents shotgun debugging by enforcing systematic root cause investigation before any fix is attempted. Evidence-based diagnosis catches the real problem instead of treating symptoms.
Correctness gate: a root-cause theory is a claim. Per the /verify-claims protocol, state it
with a grounded confidence % and its basis, and do not fix on it until the evidence puts it high —
a plausible-but-unverified theory produces a band-aid, not a fix.
Practices
Phase 1: Investigate
GATE: No fix proposals until investigation is complete.
-
Read the error. Fully. Not just the first line — the full stack trace, log output, and context.
-
Reproduce. Can you make it happen reliably?
- If yes: note the exact reproduction steps
- If intermittent: note the conditions under which it occurs and doesn't occur
-
Recall related memory. Before investigating further:
- Search
.memory/gotchas/for entries related to the error message, affected files, or domain area - Search
.memory/patterns/for entries about how similar code paths work - If a relevant gotcha exists, test it as your first hypothesis
- Search
-
Check what changed. What's different from when it last worked?
git log --oneline -10— recent commitsgit diff— uncommitted changes- Environment changes (new dependency versions, config changes)
-
Gather evidence. Before forming theories:
- Read the failing code path line by line
- Add temporary logging/debugging output at key points
- Check input data — is it what you expect?
- Check database state — are records in the expected state?
- If tech-context loaded: use stack-specific tools (e.g.,
rails console,binding.pry)
Phase 2: Pattern Analysis
-
Find a working example. Is there similar code that works correctly?
- Compare the working and broken versions
- What's different?
-
Check for known patterns. Cross-reference findings with
.memory/gotchas/recalled in step 3.
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 Changed · +1 lines 174c4c3e5f72
- 2mo ago First seen · 149 lines · 48 tokens per session scan A 01d49750f8a5
debugging is a skill published in the GitHub repository jstoup111/ai-conductor (7 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 1,608 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
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…