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.
git 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/rules/lubochka/xiigen-general-skills/xiigen-systematic-debugging)<a href="https://agentmods.dev/rules/lubochka/xiigen-general-skills/xiigen-systematic-debugging"><img src="https://agentmods.dev/badge/rules/lubochka/xiigen-general-skills/xiigen-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.00000 | $0.00178 |
| Opus 5 | $0.00000 | $0.00089 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
xiigen-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 7d 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.
- 7d ago First seen · 35 lines · 0 tokens per session scan A 82ab763f76f3
xiigen-systematic-debugging is a cursor rule published in the GitHub repository lubochka/xiigen-general-skills (1 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 178 tokens. 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 cursor rules, from other repositories
bug-hunter
Incident Responder & Debugger (Trigger with raw logs).
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
context-delegate
Context Gatherer & External LLM Prompt Generator.
claude-skills-karpathy
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.