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 agentmods add rules/danielvm-git/bigpowers/diagnose-rootgit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/danielvm-git/bigpowers/diagnose-root)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/diagnose-root"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/diagnose-root.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 | $0.00042 | $0.00297 |
| Opus 5 | $0.00021 | $0.00148 |
| Sonnet 5 | $0.00008 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
diagnose-root 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 today.
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
Diagnose Root
Boundary: Canonical, reusable 4-phase RCA engine. Invoked by investigate-bug (as step 2 of the end-to-end flow) and by fix-bug (when no bug file exists). Does not write the bug file — that is investigate-bug's responsibility.
Four phases — do not skip. Update the active specs/bugs/BUG-*.md file at each phase.
Phases
- Reproduce — minimal steps; record environment; capture logs.
- Isolate — narrow to module/function; binary-search commits or config.
- Hypothesize — list ranked hypotheses with falsification test each.
- Verify — run falsification; confirm single root cause; link to fix plan.
HARD GATE — Do not propose a fix until phase 4 confirms one root cause with evidence.
Verify
→ verify: [ "$(grep -lE 'Reproduce' specs/bugs/BUG-*.md 2>/dev/null | grep -cv "\.okf\.md$")" -ge 1 ]
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.
- today First seen · 24 lines · 42 tokens per session scan A e8f579d36c12
diagnose-root is a cursor rule published in the GitHub repository danielvm-git/bigpowers (162 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 297 once invoked, about $0.0002 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
context-os
ContextOS rules for context-os.
database
Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.
vue
Rules for Vue (2 and 3) single-file components.
nextjs
ContextOS rules for nextjs.