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/kareemessam09/openship-app/systematic-debuggingnpx skills add kareemessam09/Openship-App --skill systematic-debugginggit clone --depth 1 https://github.com/kareemessam09/Openship-AppWrote 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/kareemessam09/openship-app/systematic-debugging)<a href="https://agentmods.dev/skills/kareemessam09/openship-app/systematic-debugging"><img src="https://agentmods.dev/badge/skills/kareemessam09/openship-app/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.00040 | $0.00243 |
| Opus 5 | $0.00020 | $0.00121 |
| Sonnet 5 | $0.00008 | $0.00049 |
| Haiku 4.5 | $0.00004 | $0.00024 |
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 3d 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 Superpower
Mandates a structured root-cause analysis process. Never guess or apply speculative patches.
The 4 Phases of Debugging
1. Root Cause Tracing
- Reproduce the failure consistently.
- Collect full stack traces, log outputs, and exact inputs that triggered the defect.
- Identify the exact line, contract violation, or state mismatch causing the failure.
2. Pattern Analysis
- Inspect similar usages across the codebase.
- Check if this is an isolated bug or part of a systemic architectural pattern.
3. Hypothesis & Testing
- Formulate a testable hypothesis explaining why the bug occurred.
- Write a failing reproduction test that isolates this exact condition.
4. Minimal Targeted Fix & Verification
- Apply the minimal code change that satisfies the reproduction test.
- Re-run full test suites to ensure no regressions are introduced.
- Remove temporary debug logs or scaffolding.
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.
- 3d ago First seen · 29 lines · 40 tokens per session scan A 6acb26220b70
systematic-debugging is a skill published in the GitHub repository kareemessam09/Openship-App (11 stars, last pushed 8d ago), licensed Apache-2.0. It adds 40 tokens to every session and 243 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…