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 skills add lubochka/xiigen-general-skills --skill systematic-debugginggit clone --depth 1 https://github.com/lubochka/xiigen-general-skillsWrote 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/lubochka/xiigen-general-skills/systematic-debugging)<a href="https://agentmods.dev/skills/lubochka/xiigen-general-skills/systematic-debugging"><img src="https://agentmods.dev/badge/skills/lubochka/xiigen-general-skills/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.00024 | $0.00173 |
| Opus 5 | $0.00012 | $0.00086 |
| Sonnet 5 | $0.00005 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
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 8d 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
Purpose
Make debugging reproducible and disciplined.
When to Use
Use for unclear failures, regressions, or unstable behavior.
Inputs
Symptoms, hypotheses, commands, code boundaries, observations.
Steps
- Write down hypotheses.
- Test one hypothesis at a time.
- Record the observation.
- Update the hypothesis list before changing direction.
Gates
Debugging has a clear trail of tested ideas and outcomes.
Evidence
Debug notes, command output, reduced repro, or identified culprit.
Anti-Patterns
Random edits, mixed hypotheses, and unrecorded attempts.
Related
debug-session, root-cause-tracing
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.
- 8d ago First seen · 34 lines · 24 tokens per session scan A 395d58800f64
systematic-debugging is a skill published in the GitHub repository lubochka/xiigen-general-skills (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 173 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-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
review-diff
Scan git diffs for project-specific anti-patterns. Triggers on: 'scan diff', 'check diff', 'anti-pattern check', 'pattern scan', 'review changes'.
triage-issue
Verify an issue, persisted audit finding, or unresolved review finding against current code, classify it, and write only the contracted forge/ledger outcome. Supports independent batches and an immediate-fix review-finding route. Triggers: "triage-issue", "triage issue N", "triage this finding", "is this trigger met".
pdlc-perf
A workflow for finding and improving performance problems in a specified backend service or frontend application. It examines areas such as database queries, caching, response times, loading, rendering, and network use, then records its findings in a report.
pdlc-lint
A code-quality checker that runs static analysis, style checks, type checks, and other project-configured tools. It supports checking, safely fixing eligible problems, and setting up a lint toolchain.
pdlc-fix
An automated bug-fixing workflow that locates a reported bug, reproduces it with a test, applies a minimal fix, runs tests, and updates the relevant documentation.