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 Notysoty/openagentskills --skill bug-root-cause-analyzergit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/bug-root-cause-analyzer)<a href="https://agentmods.dev/skills/notysoty/openagentskills/bug-root-cause-analyzer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/bug-root-cause-analyzer.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.00020 | $0.01643 |
| Opus 5 | $0.00010 | $0.00822 |
| Sonnet 5 | $0.00004 | $0.00329 |
| Haiku 4.5 | $0.00002 | $0.00164 |
Grade A, and why
Bug Root Cause Analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Root Cause Analyzer
What this skill does
This skill directs the agent to work through a bug methodically — distinguishing the root cause from the symptoms, tracing the execution path that led to the failure, and producing a clear diagnosis before suggesting a fix. It applies the 5-Why technique, reads stack traces carefully, and avoids the trap of patching the symptom without understanding the cause.
Use this when you have a bug that isn't immediately obvious, when a quick fix didn't hold, or when you want to understand why something broke before deciding how to fix it.
How to use
Claude Code / Cline
Copy this file to .agents/skills/bug-root-cause-analyzer/SKILL.md in your project root.
Then ask:
- "I'm getting a TypeError in checkout. Use the Bug Root Cause Analyzer skill to diagnose it."
- "This test is flaky and I don't know why. Use the Bug Root Cause Analyzer skill."
Provide as much context as you can: the error message, the stack trace, the relevant code, and what you expected to happen.
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane before describing the bug.
The Prompt / Instructions for the Agent
When asked to diagnose a bug, follow this process:
Phase 1 — Gather information
Before analyzing, make sure you have:
- The exact error message (not paraphrased)
- The full stack trace if available
- The code where the error originates
- What the user expected to happen vs what actually happened
- When the bug started (after a deploy? a specific change?)
If any of these are missing, ask for them before proceeding.
Phase 2 — Read the stack trace
- Start at the top of the stack trace — this is where the error was thrown, not necessarily where the bug lives.
- Work downward through the frames until you reach application code (skip framework internals unless you have good reason to look there).
- Identify the last application-code frame before the error — this is usually where the bug lives.
- Note the call chain from entry point to failure point.
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 · 170 lines · 20 tokens per session scan A 2ccafd1ae844
Bug Root Cause Analyzer is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 23d ago), licensed MIT. It adds 20 tokens to every session and 1,643 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
analyze-project
Forensic root cause analyzer for Antigravity sessions. Classifies scope deltas, rework patterns, root causes, hotspots, and auto-improves prompts/health.
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
ast-grep
Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.
debugging
Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test. Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
lcx-doctor
Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install…