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/jpm1118/threadwork/systematic-debuggingnpx skills add JPM1118/Threadwork --skill systematic-debugginggit clone --depth 1 https://github.com/JPM1118/ThreadworkWhat 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.00000 | $0.01945 |
| Opus 5 | $0.00000 | $0.00972 |
| Sonnet 5 | $0.00000 | $0.00389 |
| Haiku 4.5 | $0.00000 | $0.00194 |
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 yesterday.
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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging Skill
Resolve issues through root cause discovery rather than random fix attempts. This skill prevents thrashing and achieves 95%+ first-time fix rates.
Core Principle
UNDERSTAND BEFORE YOU FIX
Random fix attempts waste time and often introduce new bugs. Systematic investigation finds the real problem.
When to Use This Skill
Use this skill when:
- Tests are failing
- A feature isn't working as expected
- You encounter an error message
- Something that worked before is now broken
- You're tempted to "just try something"
The Four-Phase Framework
┌─────────────────────────────────────────────────────────────┐
│ Systematic Debugging Flow │
├─────────────────────────────────────────────────────────────┤
│ │
│ Phase 1: INVESTIGATE │
│ ↓ Read errors, reproduce, examine changes │
│ │
│ Phase 2: ANALYZE │
│ ↓ Find working examples, compare patterns │
│ │
│ Phase 3: HYPOTHESIZE │
│ ↓ Form theories, test with minimal changes │
│ │
│ Phase 4: IMPLEMENT │
│ Create failing test, implement fix, verify │
│ │
└─────────────────────────────────────────────────────────────┘
Phase 1: Root Cause Investigation
Step 1.1: Read the Error Carefully
Don't skim. Read the ENTIRE error message:
- Error type/name
- Error message
- Stack trace (every line)
- File paths and line numbers
- Any additional context
# Run the failing test/command
npm test -- --grep "failing test name"
# Read ALL output, not just the failure summary
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.
- yesterday First seen · 315 lines · 0 tokens per session scan A 87816f0f5522
systematic-debugging is a skill published in the GitHub repository JPM1118/Threadwork (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,945 tokens. 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…
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…
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…