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/radumarias/xorio-claude-pluginWrote 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/commands/radumarias/xorio-claude-plugin/root-cause)<a href="https://agentmods.dev/commands/radumarias/xorio-claude-plugin/root-cause"><img src="https://agentmods.dev/badge/commands/radumarias/xorio-claude-plugin/root-cause/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/commands/radumarias/xorio-claude-plugin/root-cause"><img src="https://agentmods.dev/badge/commands/radumarias/xorio-claude-plugin/root-cause.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.00037 | $0.01092 |
| Opus 5.5 | $0.00015 | $0.00437 |
| Sonnet 5.5 | $0.00007 | $0.00218 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
root-cause 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Root Cause Analysis
Identify the most plausible root cause of the given problem — grounded in evidence, not speculation.
Problem
$ARGUMENTS
Mode select
Parse $ARGUMENTS for the --deep flag (strip it from the problem text):
- absent → Light mode (default): a single evidence-grounded 5 Whys pass. Fast, cheap, interactive-friendly. Best for a well-scoped problem.
- present → Deep mode: a multi-agent causal-tree investigation via the Workflow tool. Use for gnarly, ambiguous, or likely-multi-cause failures. Costs more —
--deepis the explicit opt-in to multi-agent orchestration.
Light mode (default) — evidence-grounded 5 Whys
Apply the "5 Whys" — "five" is a guideline; iterate more or fewer times until you reach a root cause or detect a cycle. Two rules separate a real RCA from a guess:
- Ground every link before accepting it. Each "because" is a claim — prove it against the system, don't assert it:
- what changed / when →
git log/git blame/ (if it narrows it)git bisect - the code behaves as claimed → grep/read the path; better, run the repro or the failing test
- cite the evidence inline (
file:line, commit SHA, command + output). A link you can't ground is a hypothesis, not a cause — label it so.
- what changed / when →
- Don't tunnel. At the first "why", list 2–4 candidate causes, not one; pursue the best-evidenced. Before concluding, name at least one alternative branch and state what evidence rules it out. Convergence from two angles beats a single chain.
State the problem, then iterate: answer → ground → "why?" → … Keep a running record (see Output). Stop at the root cause (or a detected cycle), then conclude.
Deep mode (--deep) — parallel, verified causal tree
Drive this with the Workflow tool (dynamic fan-out → pipeline); a simple case may run inline with parallel Task agents instead. Resolve model tiers at runtime — never hardcode model names: STRONG = the most capable model available (from the session environment), MID = one tier below (cheaper, mechanical/structured work), LIGHT = the cheapest (trivial gates). If the ranking is unclear, omit the model and inherit the session model.
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.
- 1mo ago First seen · 67 lines · 37 tokens per session scan A 33b9b2855ffe
root-cause is a command published in the GitHub repository radumarias/xorio-claude-plugin (3 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 1,092 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.