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 DollarDill/beads-superpowers --skill using-superpowersgit clone --depth 1 https://github.com/DollarDill/beads-superpowersWrote 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/dollardill/beads-superpowers/using-superpowers)<a href="https://agentmods.dev/skills/dollardill/beads-superpowers/using-superpowers"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/using-superpowers.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.00029 | $0.01191 |
| Opus 5 | $0.00015 | $0.00596 |
| Sonnet 5 | $0.00006 | $0.00238 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
using-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 6d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. You cannot rationalize your way out of this.
The Rule
Invoke relevant or requested skills BEFORE any response or action — including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to use it.
Before entering plan mode: if you haven't already brainstormed, invoke the brainstorming skill first.
Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, track it with beads (see Beads below) — TodoWrite is forbidden.
Skill Priority
Process skills come first — they set the approach, implementation skills carry it out. Implementation is spec-backed: it starts from an approved spec or plan, and you state the file you are working from before the first edit.
- "Let's build X" → beads-superpowers:brainstorming first, then implementation skills.
- "Fix this bug" → beads-superpowers:systematic-debugging first, then domain skills.
- No spec or plan file yet, and it's more than a typo? Brainstorm before you edit.
Red Flags
These thoughts mean STOP—you're rationalizing:
| Thought | Reality |
|---|---|
| "I need more context first" / "let me explore the codebase first" / "I can check git/files quickly" / "let me gather information first" / "I'll just do this one thing first" | Skills tell you HOW. Check BEFORE doing anything. |
| "This is just a simple question" / "this doesn't need a formal skill" / "this doesn't count as a task" / "the skill is overkill" | Action = task. If a skill exists, use it. Simple things become complex. |
| "I remember this skill" | Skills evolve. Read current version. |
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
| "This bead is specified enough — I'll just implement it" | Spec-backed: name the spec/plan file, or brainstorm first. |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 86 lines · 29 tokens per session scan A b95df64d0c21
using-superpowers is a skill published in the GitHub repository DollarDill/beads-superpowers (26 stars, last pushed 15d ago), licensed MIT. It adds 29 tokens to every session and 1,191 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-30.
Other skills, from other repositories
beads-onboard
This skill should be used when the user asks to "onboard beads", "set up beads conventions", "configure beads for this project", "set up project labels", "improve my beads quality", "run beads onboard", "upgrade beads conventions", "re-run beads onboard", or when a project has .beads/ but no .beads/conventions/…
pr-review
Use when the user wants to deeply review a pull/merge request or a local diff — "review this PR", "grill the MR", "stress-test this diff", "deep-dive code review", "code review before merge", or when they name a PR/MR URL, number, branch, commit range (A..B/A...B), tag or SHA. Works on GitHub (gh), GitLab (glab), or a…
codex
Run the Codex CLI directly in the user's checkout for code analysis, refactoring, or automated editing without Claude Architect's verified delegation lifecycle.
explain
Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where to start if you need to change it. Do…
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
shipyard-handoff
Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress.