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 root-cause-tracinggit 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/root-cause-tracing)<a href="https://agentmods.dev/skills/lubochka/xiigen-general-skills/root-cause-tracing"><img src="https://agentmods.dev/badge/skills/lubochka/xiigen-general-skills/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/skills/lubochka/xiigen-general-skills/root-cause-tracing"><img src="https://agentmods.dev/badge/skills/lubochka/xiigen-general-skills/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.00028 | $0.00187 |
| Opus 5 | $0.00014 | $0.00093 |
| Sonnet 5 | $0.00006 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
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 11d 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.
- 11d ago First seen · 34 lines · 28 tokens per session scan A 1810dcd3c4ac
root-cause-tracing is a skill published in the GitHub repository lubochka/xiigen-general-skills (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 187 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.
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".
review-diff
Scan git diffs for project-specific anti-patterns. Triggers on: 'scan diff', 'check diff', 'anti-pattern check', 'pattern scan', 'review changes'.
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.