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/jeremydev87/codingbuddy/systematic-debuggingnpx skills add JeremyDev87/codingbuddy --skill systematic-debugginggit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWrote 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/jeremydev87/codingbuddy/systematic-debugging)<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/systematic-debugging"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/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.00021 | $0.02713 |
| Opus 5 | $0.00010 | $0.01357 |
| Sonnet 5 | $0.00004 | $0.00543 |
| Haiku 4.5 | $0.00002 | $0.00271 |
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 — 337 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.
Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
Violating the letter of this process is violating the spirit of debugging.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phase 1, you cannot propose fixes.
Mandatory 6-Step Debugging Sequence
Before ANY debugging attempt, follow this sequence in order:
- Validate/Check command — If the external tool has a validate/check/lint command, run it FIRST. Always. No exceptions.
- Official documentation — Verify system behavior by reading official docs. No guessing how a system works.
- Hypothesis formation — Form a hypothesis with evidence from steps 1-2.
- Fix implementation — Implement the fix based on your hypothesis.
- Local verification — Verify the fix locally before shipping.
- Ship — Only ship after local verification passes.
Validate First Rule
If an external tool, service, or configuration format has a validate/check/lint command, you MUST run it BEFORE any debugging or fix attempts:
| Tool/Format | Validate Command |
|---|---|
| GitHub Actions | actionlint or validate via act --list |
| Docker | docker compose config |
| Kubernetes | kubectl apply --dry-run=client |
| Terraform | terraform validate |
| JSON | jq . or schema-specific validators |
| YAML | yamllint |
| TypeScript | tsc --noEmit |
| ESLint config | eslint --print-config |
Why: Validation catches syntax and schema errors instantly. Debugging without validation wastes time on issues the tool itself can detect.
Verify Mental Model Rule
Before assuming how an external system works, read the official documentation first:
- Never guess API behavior, config format, or tool behavior from memory
- Always verify against official docs, especially for version-specific behavior
- Check changelogs when upgrading — behavior may have changed between versions
- If official docs are unavailable, use
--help, man pages, or source code as reference
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 · 337 lines · 21 tokens per session scan A 3878ad156fa1
systematic-debugging is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 2,713 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…
ring:checking-frontend-quality
Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for…
bzdesignprompt
为前端或网页设计任务选择并下载合适的 DESIGN.md 模板。当用户需要网页设计模板、UI 风格参考、设计系统、落地页或前端界面设计时，浏览长亭百智云 UI 设计模板库，根据产品场景和视觉偏好匹配模板，并将完整 DESIGN.md 保存到项目中。.
verify-quality
Verify code quality including naming conventions, organization, documentation, and general best practices. Use when asked to "verify quality", "check code quality", or "review code organization".