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/stivi7/cyberpunk-context-runners/systematic-debuggingnpx skills add Stivi7/cyberpunk-context-runners --skill systematic-debugginggit clone --depth 1 https://github.com/Stivi7/cyberpunk-context-runnersWrote 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/stivi7/cyberpunk-context-runners/systematic-debugging)<a href="https://agentmods.dev/skills/stivi7/cyberpunk-context-runners/systematic-debugging"><img src="https://agentmods.dev/badge/skills/stivi7/cyberpunk-context-runners/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.1 | $0.00026 | $0.00280 |
| Opus 5 | $0.00013 | $0.00140 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
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 5d 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
Metadata
- Version: 1.0.0
- Triggers: Bug, failing check, unexplained output, or repeated review finding
- Allowed agents: Operator, Daemon, Neon, Grid Master, Gatekeeper
- Side effects: May add diagnostics, tests, or implementation changes
When to Use
Use before proposing a fix. Do not repeat an unchanged attempt without a changed hypothesis.
Inputs
Observed failure, reproduction, relevant code, recent diff, environment, baseline evidence, and prior attempts.
Procedure
- Reproduce and preserve the exact failure.
- Separate regression, baseline failure, environment issue, and incorrect expectation.
- Trace data and control flow to the earliest incorrect state.
- Form one falsifiable root-cause hypothesis.
- Add the smallest test or diagnostic that distinguishes the hypothesis.
- Change the root cause, then rerun focused and broader verification.
- After repeated failure, discard the hypothesis and re-diagnose.
Verification
The reproduction must fail before the fix, pass after it, and leave related verification green.
Output
Root cause, evidence, regression test, change, verification results, and rejected hypotheses.
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.
- 5d ago First seen · 40 lines · 26 tokens per session scan A c8c91412bd33
systematic-debugging is a skill published in the GitHub repository Stivi7/cyberpunk-context-runners (4 stars, last pushed 5d ago), licensed MIT. It adds 26 tokens to every session and 280 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-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…