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/rolandbrecht/agent-skills/systematic-debuggingnpx skills add rolandbrecht/agent-skills --skill systematic-debugginggit clone --depth 1 https://github.com/rolandbrecht/agent-skillsWrote 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/rolandbrecht/agent-skills/systematic-debugging)<a href="https://agentmods.dev/skills/rolandbrecht/agent-skills/systematic-debugging"><img src="https://agentmods.dev/badge/skills/rolandbrecht/agent-skills/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.00064 | $0.01018 |
| Opus 5 | $0.00032 | $0.00509 |
| Sonnet 5 | $0.00013 | $0.00204 |
| Haiku 4.5 | $0.00006 | $0.00102 |
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging
Overview
Random fixes waste time and create new bugs. Quick patches mask underlying issues. As an AI agent, it is tempting to rapidly guess the solution based on symptoms because it is fast. You must resist this temptation.
Core principle: ALWAYS find the root cause before attempting fixes. The Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
When to Use
Use for ANY technical issue:
- Test failures
- Bugs in production or local development
- Build or CI pipeline failures
- Unexplained performance issues
Do not skip this process even if:
- The issue seems "simple" or "obvious"
- You are under time pressure
- The user asks for a "quick fix"
Phase 1: Planning (Root Cause Investigation)
BEFORE attempting ANY code modification or fix:
-
Information Gathering (Do Not Guess)
- Read the error message and stack trace completely. Note the exact file paths and line numbers.
- Use
view_fileto read the surrounding code where the error occurred. - Use
grep_searchto find definitions, usages, or configurations related to the failing components. - Never assume you know what a file contains without checking or listing its directory.
-
Reproduce and Isolate
- Can you trigger the bug reliably? If there isn't an existing test, write a minimal, standalone reproduction script (e.g.,
repro.pyor.jsin/tmp/) usingwrite_to_fileand then execute it viarun_command. - If you cannot reproduce it locally, you must gather more data. Do not guess the fix.
- Can you trigger the bug reliably? If there isn't an existing test, write a minimal, standalone reproduction script (e.g.,
-
Map the Boundaries (Multi-Component Systems)
- If the system has multiple layers (e.g., Frontend → API → Database), do not guess which layer failed.
- Inject telemetry temporarily: Use
replace_file_contentto addconsole.log,print(), or logger statements at the boundary of each component. - Run the system once to see exactly what data entered and exited each layer.
Phase 2: Execution (Hypothesis & Minimal Fix)
What ships with it
2 files 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 · 97 lines · 64 tokens per session scan A 29344ce48cdd
systematic-debugging is a skill published in the GitHub repository rolandbrecht/agent-skills (4 stars, last pushed 21d ago), licensed MIT. It adds 64 tokens to every session and 1,018 once invoked, about $0.0003 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
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
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…
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
lattice-init
Guided setup and upgrade-check experience for Lattice projects -- scans the repository, detects existing configuration and outdated conventions, suggests refiners and available upgrades in priority order, and creates or reconciles the .lattice/ config. Bridges the gap between installing skills and getting first value…
intelligent-investor-graham
Use Graham value investing for Is this investment or speculation, defensive stock screens, margin of safety, Mr. Market, allocation, funds, IPOs.