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 Omar-Obando/qwen-orchestrator --skill debugginggit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/debugging)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/debugging"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/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/omar-obando/qwen-orchestrator/debugging"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/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.00029 | $0.00969 |
| Opus 5.5 | $0.00012 | $0.00388 |
| Sonnet 5.5 | $0.00006 | $0.00194 |
| Haiku 4.5 | $0.00003 | $0.00097 |
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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Skill — Systematic Investigation
This skill provides a structured approach to debugging that replaces guessing with evidence-based investigation.
Debugging Methodology
OBSERVE → HYPOTHESIZE → TEST → FIX → VERIFY
Phase 1: OBSERVE (Collect Evidence)
- What is the exact error message?
- What is the expected behavior?
- What is the actual behavior?
- When does it happen? (always, sometimes, specific conditions?)
- What changed recently? (code, config, dependencies, environment)
Phase 2: HYPOTHESIZE (Form Theories)
- List at least 3 possible causes
- Rank by probability (most likely first)
- For each: what evidence would prove/disprove it?
Phase 3: TEST (Verify Hypothesis)
- Test ONE hypothesis at a time
- Change ONLY ONE variable per test
- Record all observations
- Stop when you find the root cause
Phase 4: FIX (Apply Fix)
- Make the MINIMAL change that fixes the issue
- Do NOT refactor while fixing
- Write a test that reproduces the bug FIRST
- Then implement the fix
Phase 5: VERIFY (Confirm Fix)
- Original test now passes
- No new failures introduced
- Edge cases still work
- Similar code paths checked
Investigation Techniques
Binary Search Debugging
1. Find the midpoint of the execution path
2. Check state at that point
3. If correct: bug is AFTER midpoint
4. If incorrect: bug is BEFORE midpoint
5. Repeat until isolated
Rubber Duck Debugging
1. Explain the code line by line
2. Explain what each variable should be
3. Explain what the output should be
4. The act of explaining often reveals the bug
Log-Based Debugging
// Strategic logging for debugging
console.log('[DEBUG] Input:', { userId, filters, pagination });
console.log('[DEBUG] Query result:', { count, firstItem, lastItem });
console.log('[DEBUG] Transform:', { input, output, duration });
Common Bug Categories
| Category | Symptoms | Investigation |
|---|---|---|
| Off-by-one | Wrong count, missing last item | Check boundary conditions |
| Race condition | Intermittent, timing-dependent | Add logging, check async flow |
| Null reference | TypeError: Cannot read property | Check all property access |
| Type coercion | Unexpected comparison results | Use strict equality (===) |
| Stale state | UI doesn't reflect changes | Check state update mechanism |
| Memory leak | Increasing memory over time | Profile heap, check cleanup |
| Circular reference | Stack overflow, infinite loop | Trace the reference chain |
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.
- 1mo ago First seen · 157 lines · 29 tokens per session scan A 54e87843bb2d
debugging is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (52 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 969 once invoked, about $0.0001 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-30.
Other skills, from other repositories
loopx-self-repair
Diagnose and repair LoopX control-plane drift or agent behavior drift. Use when a LoopX task makes unexpectedly small progress, follows a stale or contradictory recommendedaction, ignores a higher-priority blocked item while doing fallback work, reports vague owner/user gates, loses todo projection, misaligns…
code-review
Review diffs and change sets for bugs, regressions, risks, and missing tests.
code-coherence-review
Reviews code and plans for logic coherence, correctness, and structural integrity.
b3os-ai-code-safety
As code and logic grow, the cost is not the happy path — it is coupling: a change ripples into places you did not touch, and a "small fix" breaks something unrelated. This skill is a code-structure and refactoring guide: structure well from the initial design so a change stays local, apply operational safety where…
graphify
Navigate a codebase through a local tree-sitter knowledge graph instead of grepping blindly. Use when asked how a medium-or-large codebase works, where a symbol is defined, what calls what, how two modules connect, or when planning a refactor that spans files. Requires the external graphify Python CLI; degrades to…
refire
Turns confirmed findings from a taste into one scoped fix run, then re-verifies each finding at its cited location. Use after /sous-chef:taste when the user says to fix the findings, apply the review, or refire it. Not for new feature work - that is a fresh /sous-chef:fire.