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.
git clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/agents/fabioc-aloha/alex_skill_mall/systematic-debugging)<a href="https://agentmods.dev/agents/fabioc-aloha/alex_skill_mall/systematic-debugging"><img src="https://agentmods.dev/badge/agents/fabioc-aloha/alex_skill_mall/systematic-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/agents/fabioc-aloha/alex_skill_mall/systematic-debugging"><img src="https://agentmods.dev/badge/agents/fabioc-aloha/alex_skill_mall/systematic-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.00028 | $0.00368 |
| Opus 5.5 | $0.00011 | $0.00147 |
| Sonnet 5.5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
systematic-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
Systematic Debugging
Structured 4-phase debugging: problem assessment → root cause investigation → targeted fix → quality assurance with regression tests.
When to Use
- Diagnosing a bug that isn't immediately obvious
- Tracing through complex execution paths
- When the failing commit is unknown (git bisect)
- Debugging race conditions, state issues, or environment failures
- Any bug where "just looking at it" hasn't worked
Phases
Phase 1: Problem Assessment
- Gather context: errors, stack traces, reproduction steps, expected vs actual
- Reproduce before fixing
Phase 2: Investigation
- Trace execution path from entry to error
- Check recent changes (
git log --oneline -10 -- <file>) - Form hypotheses ranked by likelihood: data → logic → state → environment
- Plan verification for each
Phase 3: Resolution
- Targeted minimal fix addressing root cause
- Follow existing patterns; add defensive programming
- Verify: run tests, reproduce original, broader regression suite
Phase 4: Quality Assurance
- Add regression test
- Check for same pattern elsewhere
- Report: Bug → Root Cause → Fix → Files → Test
Guidelines
- Systematic: follow phases, don't jump to solutions
- Simplest hypothesis first
- Never fix without understanding root cause
- Small testable changes over large refactors
- Use
git bisectfor unknown failure commits
Source
Adapted from awesome-copilot/agents/debug.agent.md and awesome-claude-code-toolkit/plugins/bug-detective/.
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 · 51 lines · 28 tokens per session scan A 1106d19ed965
systematic-debugging is an agent published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (5 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 368 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-09-03.
Other agents, from other repositories
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
retrospective
../../src/claude/agents/retrospective.md.
Dynatrace Expert
The Dynatrace Expert Agent integrates observability and security capabilities directly into GitHub workflows, enabling development teams to investigate incidents, validate deployments, triage errors, detect performance regressions, validate releases, and manage security vulnerabilities by autonomously analysing…
Power BI Performance Expert Mode
Expert Power BI performance optimization guidance for troubleshooting, monitoring, and improving the performance of Power BI models, reports, and queries.
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.