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/eilodon/dps-superskills-mcp/systematic-debuggingnpx skills add Eilodon/DPS-Superskills-MCP --skill systematic-debugginggit clone --depth 1 https://github.com/Eilodon/DPS-Superskills-MCPWrote 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/eilodon/dps-superskills-mcp/systematic-debugging)<a href="https://agentmods.dev/skills/eilodon/dps-superskills-mcp/systematic-debugging"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/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.00034 | $0.01899 |
| Opus 5 | $0.00017 | $0.00949 |
| Sonnet 5 | $0.00007 | $0.00380 |
| Haiku 4.5 | $0.00003 | $0.00190 |
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 4d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging
Register: TECHNIQUE
Goal: Identify root cause with evidence before attempting any fix.
Constraints: No fix attempts before Phase 1 complete. Evidence Anchor at each phase. Confirmed fix → pattern-globalize immediately.
Adapt: the four phases below are a proven approach — adapt how you execute them to context, complexity, and available tools.
# Recent changes for context (auto-injected):
!git log --oneline -7 2>/dev/null || echo "No git history available"
Core Constraints
1. Root cause investigation completes before first fix attempt
2. Every phase produces an Evidence Anchor (not a claim — an observation)
3. Confirmed fix triggers pattern-globalize — always
Four Phases
Phase 1 — Understand the Failure
Goal: Know exactly what is broken and why — not guessing. Constraints:
- Document Evidence Anchor before forming any hypothesis: exact error text, file:line, reproduction steps
- If not reproducible → gather more data. Do not guess.
- Multi-component system → instrument each boundary before hypothesizing
# Evidence Anchor format:
Error: "<exact message>"
Location: <file>:<line>
Reproducible: YES | NO | INTERMITTENT
Recent change: <git sha> — <description> (from !git log above)
Instrument at boundaries when system has multiple components:
echo "=== Component A output: ===" && <check>
echo "=== Component B input: ===" && <check>
# Find WHERE it breaks, then investigate that component
Phase 2 — Find the Pattern
Goal: Understand the structural cause, not just the specific instance. Constraints:
- Find a working example of similar code in the codebase before proposing a fix
- Read reference implementations completely — no skimming
- List every difference between working and broken, however small
Evidence Anchor: "Working: <file>:<line> | Broken: <file>:<line> | Difference: <what differs>"
Phase 3 — Hypothesis and Test
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.
- 4d ago First seen · 193 lines · 34 tokens per session scan A 0a3b30068b46
systematic-debugging is a skill published in the GitHub repository Eilodon/DPS-Superskills-MCP (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,899 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-31.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…