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/michaelpersonal/superpowers-cursor-rulesWrote 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/michaelpersonal/superpowers-cursor-rules/superpowers)<a href="https://agentmods.dev/rules/michaelpersonal/superpowers-cursor-rules/superpowers"><img src="https://agentmods.dev/badge/rules/michaelpersonal/superpowers-cursor-rules/superpowers/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/michaelpersonal/superpowers-cursor-rules/superpowers"><img src="https://agentmods.dev/badge/rules/michaelpersonal/superpowers-cursor-rules/superpowers.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.07429 | $0.07429 |
| Opus 5.5 | $0.02972 | $0.02972 |
| Sonnet 5.5 | $0.01486 | $0.01486 |
| Haiku 4.5 | $0.00743 | $0.00743 |
Grade A, and why
superpowers 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 1,075 lines · 7,429 tokens per session scan A 43cde831ffdc
superpowers is a cursor rule published in the GitHub repository michaelpersonal/superpowers-cursor-rules (18 stars, last pushed 8mo ago), with no licence file. It adds 7,429 tokens to every session, about $0.0297 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-30.
Other cursor rules, from other repositories
fix-bug
Bug fix orchestrator — activeflow fixbug; reads specs/bugs/BUG-.md; chains investigate-bug, develop-tdd, validate-fix. Use when user reports a defect.
investigate-bug
Investigate a bug or issue by exploring the codebase to find root cause, then write a TDD-based fix plan to specs/bugs/BUG-.md. Use when user reports a bug, wants to investigate a problem, mentions "triage", or wants to plan a fix.
investigate
Root-cause a bug, test failure, CI failure, or unexpected behavior before changing code. Reproduce, compare against working code, test one hypothesis at a time, then fix with a failing regression test first. Stops after three failed fixes to question the design, and requires fresh evidence before any "fixed" claim.…
debug-issue
When the user reports a bug, an error, or unexpected behavior. Enforces four structured phases — reproduction, failing test, root cause isolation, fix and verify — to stop guess-and-check loops.
bug-fix-tdd-guard
A rule for fixing software bugs with test-driven development, or TDD: first reproduce the bug, then write a test that fails, then make the smallest code change that passes it, and finally run the full checks.
bug-fix
Light skill: TDD pipeline for bug fixes. Regression test first, then fix. Can auto-invoke when the user reports a bug, describes unexpected behavior, or asks to fix an issue.