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 skills add modimihir07/agentic-os --skill systematic-debuggit clone --depth 1 https://github.com/modimihir07/agentic-osWrote 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/modimihir07/agentic-os/systematic-debug)<a href="https://agentmods.dev/skills/modimihir07/agentic-os/systematic-debug"><img src="https://agentmods.dev/badge/skills/modimihir07/agentic-os/systematic-debug/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/skills/modimihir07/agentic-os/systematic-debug"><img src="https://agentmods.dev/badge/skills/modimihir07/agentic-os/systematic-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.00248 |
| Opus 5.5 | $0.00004 | $0.00099 |
| Sonnet 5.5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
systematic-debug 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
Description
Four-phase debugging methodology: reproduce, investigate, fix, verify. Prevents guesswork and ensures root cause is found before any fix is applied.
When to Use
- Encountering a bug or error
- System failure or crash
- Unexplained behavior
- Performance regression
Process
- Reproduce: Capture exact steps, environment, and error output
- Investigate: Trace root cause through logs, stack traces, and code analysis
- Fix: Apply minimal fix addressing root cause (not symptoms)
- Verify: Confirm fix resolves the issue and doesn't introduce regressions
- Update learnings.md with debugging insights
Safety
- If 3 fix attempts fail, trigger architectural review
- Never apply workaround without understanding root cause
Output
Debug report: symptoms, root cause, fix applied, verification results
Agent Assignment
- Primary: opencode
What ships with it
3 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.
- 1mo ago First seen · 36 lines · 11 tokens per session scan A 31990e884a5a
systematic-debug is a skill published in the GitHub repository modimihir07/agentic-os (203 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 248 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
fix
Structured bug fix — reproduce (failing test), diagnose, fix (minimal change), verify, commit. Enforces test-first. Use when a bug needs a methodical fix.
investigate-sentry-issue
Investigate and triage a Sentry error issue.
bug-fix-workflow
Structured bug diagnosis and repair workflow using the 5-Whys root cause analysis method. Ensures fixes include tests, documentation, and knowledge capture.
triage-bug
Use when triaging a bug from session evidence (evidence-capture JSONL, replay JSONL, telemetry, repo-audit) instead of from a live user description, and producing a TDD fix plan plus a docs/bugs/{slug}.md triage artifact.
Debugging
Systematic root-cause isolation and minimal fix proposal for software bugs.
bug-fixer
A code debugging guide that diagnoses compile-time, runtime, and logic errors, then describes small fixes and checks the result with tests.