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-root-cause-tracing)<a href="https://agentmods.dev/rules/lubochka/xiigen-general-skills/xiigen-root-cause-tracing"><img src="https://agentmods.dev/badge/rules/lubochka/xiigen-general-skills/xiigen-root-cause-tracing/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/rules/lubochka/xiigen-general-skills/xiigen-root-cause-tracing"><img src="https://agentmods.dev/badge/rules/lubochka/xiigen-general-skills/xiigen-root-cause-tracing.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.00000 | $0.00190 |
| Opus 5 | $0.00000 | $0.00095 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
xiigen-root-cause-tracing 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 10d 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
Root Cause Tracing
Purpose
Find the cause behind a symptom.
When to Use
Use when a failure repeats, appears indirect, or has multiple possible causes.
Inputs
Reproduction steps, logs, changed files, dependency boundaries.
Steps
- Reproduce or isolate the symptom.
- Trace backward to the first bad point.
- Test one hypothesis at a time.
- Confirm the fix addresses the cause.
Gates
The explanation accounts for the observed symptom and the chosen fix.
Evidence
Repro notes, hypothesis checks, and before/after behavior.
Anti-Patterns
Treating downstream error messages as the root cause.
Related
failure-triage, systematic-debugging
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.
- 10d ago First seen · 35 lines · 0 tokens per session scan A d31bb254f3f6
xiigen-root-cause-tracing 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 190 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).
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.