Borrowing it
Nothing to install: this file belongs to KhourySpecialProjects/odyssey. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/KhourySpecialProjects/odyssey/production/.claude/skills/systematic-debugging/SKILL.mdgit clone --depth 1 https://github.com/KhourySpecialProjects/odysseyWrote 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/khouryspecialprojects/odyssey/systematic-debugging)<a href="https://agentmods.dev/skills/khouryspecialprojects/odyssey/systematic-debugging"><img src="https://agentmods.dev/badge/skills/khouryspecialprojects/odyssey/systematic-debugging/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/khouryspecialprojects/odyssey/systematic-debugging"><img src="https://agentmods.dev/badge/skills/khouryspecialprojects/odyssey/systematic-debugging.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00056 | $0.01125 |
| Opus 5.5 | $0.00022 | $0.00450 |
| Sonnet 5.5 | $0.00011 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00112 |
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 today.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging for Odyssey
STOP — Do Not Fix Anything Yet
Before writing a single line of fix code, complete all 4 phases. Premature fixes are the #1 cause of recurring bugs and wasted tokens.
Phase 1: Reproduce & Observe
Goal: See the bug happen. Understand exactly what occurs vs. what should occur.
-
Get the exact error. Read the error message, stack trace, or test failure output completely. Note the file, line number, and error type.
-
Reproduce it. Run the failing command:
cd frontend && npx jest path/to/failing.test.ts # test failure cd frontend && npm run dev # runtime error (check terminal + browser console) cd frontend && npm run build # build error -
Document what you see:
- Expected behavior: [what should happen]
- Actual behavior: [what actually happens]
- Error message: [exact text]
Phase 2: Trace the Root Cause
Goal: Find WHERE and WHY the bug originates — not just where it manifests.
Strategy: Follow the data flow backward from the error.
For Strapi/API errors:
- Read the request function in
lib/requests/that fetches this data - Check the Strapi schema:
backend/src/api/{type}/content-types/{type}/schema.json - Check if
fetchAPI()auto-flatten is handling the response correctly - Check cache tags — is stale data being served? (
CACHE_TAGSin the request,revalidateTag()in the action) - Check if a Server Action is using raw
fetch()withoutflattenAttributes()
For Next.js hydration mismatches:
- Check if a Server Component is accidentally using browser APIs
- Check if
"use client"is missing on an interactive component - Check for conditional rendering that differs server-side vs. client-side (e.g.,
window.innerWidth) - Check for Zustand stores being read during SSR
For test failures:
- Read the test — understand what it expects
- Read the implementation — understand what it does
- Check mocks — is
fetchAPImocked correctly? Is the mock returning flat data (not nested Strapi format)? - Check imports — is the test importing from the right path? (
@/lib/utilsvs relative)
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.
- today First seen · 106 lines · 56 tokens per session scan A ebcea033d631
systematic-debugging is a skill published in the GitHub repository KhourySpecialProjects/odyssey (7 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,125 once invoked, about $0.0002 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-10-02.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart. Do not use for ordinary review, style feedback, or general improvement suggestions.