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/thermiteau/maverick/mav-systematic-debuggingnpx skills add thermiteau/maverick --skill mav-systematic-debugginggit clone --depth 1 https://github.com/thermiteau/maverickWrote 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/thermiteau/maverick/mav-systematic-debugging)<a href="https://agentmods.dev/skills/thermiteau/maverick/mav-systematic-debugging"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/mav-systematic-debugging.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.01655 |
| Opus 5 | $0.00015 | $0.00827 |
| Sonnet 5 | $0.00006 | $0.00331 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
mav-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 5d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging
Find root cause before attempting fixes. Random fixes waste time, create new bugs, and mask underlying issues.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you have not completed Phase 1, you cannot propose fixes.
When to Use
Use for any technical issue encountered during implementation:
- Test failures
- Build errors
- Unexpected behaviour
- Integration issues
- Performance problems
Use this especially when:
- A fix attempt has already failed
- The issue seems "obvious" (obvious issues still have root causes)
- You are under pressure to move to the next step
- You do not fully understand the failure
The Four Phases
Complete each phase before proceeding to the next.
digraph debugging {
"Phase 1: Root Cause Investigation" [shape=box];
"Root cause identified?" [shape=diamond];
"Phase 2: Pattern Analysis" [shape=box];
"Phase 3: Hypothesis and Test" [shape=box];
"Hypothesis confirmed?" [shape=diamond];
"Phase 4: Fix and Verify" [shape=box];
"Fix works?" [shape=diamond];
"Done" [shape=box];
"Attempts >= 3?" [shape=diamond];
"Escalate — question architecture" [shape=box];
"Phase 1: Root Cause Investigation" -> "Root cause identified?";
"Root cause identified?" -> "Phase 2: Pattern Analysis" [label="yes"];
"Root cause identified?" -> "Phase 1: Root Cause Investigation" [label="no — gather more evidence"];
"Phase 2: Pattern Analysis" -> "Phase 3: Hypothesis and Test";
"Phase 3: Hypothesis and Test" -> "Hypothesis confirmed?";
"Hypothesis confirmed?" -> "Phase 4: Fix and Verify" [label="yes"];
"Hypothesis confirmed?" -> "Phase 3: Hypothesis and Test" [label="no — new hypothesis"];
"Phase 4: Fix and Verify" -> "Fix works?";
"Fix works?" -> "Done" [label="yes"];
"Fix works?" -> "Attempts >= 3?" [label="no"];
"Attempts >= 3?" -> "Phase 1: Root Cause Investigation" [label="no — re-investigate"];
"Attempts >= 3?" -> "Escalate — question architecture" [label="yes"];
}
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.
- 5d ago First seen · 177 lines · 30 tokens per session scan A 7f03cb798729
mav-systematic-debugging is a skill published in the GitHub repository thermiteau/maverick (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,655 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…