Borrowing it
Nothing to install: this file belongs to tutur3u/platform. 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/tutur3u/platform/main/.agents/skills/systematic-debugging/SKILL.mdgit clone --depth 1 https://github.com/tutur3u/platformWrote 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/tutur3u/platform/systematic-debugging)<a href="https://agentmods.dev/skills/tutur3u/platform/systematic-debugging"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/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/tutur3u/platform/systematic-debugging"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/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.00023 | $0.00317 |
| Opus 5.5 | $0.00009 | $0.00127 |
| Sonnet 5.5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade C, and why
systematic-debugging scanned grade C with 1 finding 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
may need targeted diagnostics. Never dump secrets or raw sensitive payloads. This is a copy
94% identical to systematic-debugging — 292 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Evidence-Driven Debugging
Find the failing boundary before changing behavior. Use the error, a reproducible case, recent changes, and a nearby working example to form a testable explanation. For a clear local defect, this can be a short inspection; a multi-service failure may need targeted diagnostics. Never dump secrets or raw sensitive payloads.
Test the smallest useful hypothesis and update it from the result. Avoid piling speculative fixes onto unexplained failures. Repeated failure is a reason to change the investigation, inspect architecture or environment, and gather new evidence; it is not an automatic requirement to stop after a fixed number of attempts.
Implement the fix within the authorized scope. Add a regression test when it captures meaningful behavior and rerun affected checks. An emergency mitigation can be useful while the root cause remains under investigation; label it accurately. Stop for user input only when progress requires a missing decision, permission, or external access.
Read these techniques only when the failure calls for them:
- root-cause-tracing.md: trace an invalid value through callers.
- condition-based-waiting.md: diagnose timing-dependent tests.
- defense-in-depth.md: choose validation boundaries after identifying a cause.
Report what failed, why the change addresses it, and what was actually verified.
What ships with it
10 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 Changed · -267 lines · +2 tokens per session scan A → C 0574ba4be0ea
- 1mo ago First seen · 297 lines · 21 tokens per session scan A 4999cb851360
systematic-debugging is a skill published in the GitHub repository tutur3u/platform (55 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 317 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (harvests environment variables). It is 94% identical to systematic-debugging, differing in 292 lines, and is treated as a copy.
Other skills, from other repositories
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
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, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
om-troubleshooter
Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
fixing-flaky-tests
Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when hogli ci:insights or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a…