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 brunob54/superpowers-orchestrator --skill using-superpowersgit clone --depth 1 https://github.com/brunob54/superpowers-orchestratorWrote 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/brunob54/superpowers-orchestrator/using-superpowers)<a href="https://agentmods.dev/skills/brunob54/superpowers-orchestrator/using-superpowers"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/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.00122 | $0.02723 |
| Opus 5 | $0.00061 | $0.01362 |
| Sonnet 5 | $0.00024 | $0.00545 |
| Haiku 4.5 | $0.00012 | $0.00272 |
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 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Superpowers
Trigger Conditions
This skill MUST be invoked when any of the following occur:
- A new session starts with a technical request
- The user gives a new task or changes topic mid-session
- Any technical work is about to begin without a skill selected
- The user asks "what should I use" or "which workflow"
Exception: Micro tasks (typo fix, single variable rename, 1-line config change) can skip the entry sequence entirely. Just do them.
When the User Names a Specific Skill
If the user's prompt references a skill by name (e.g., "use brainstorming," "use context management," "run verification"), that is a Skill tool invocation request:
- Still complete Entry Sequence steps 1–6 (token-efficiency, staleness check, etc.) — these are always-on prerequisites, not routing.
- Invoke the named skill via the
Skilltool. Do not re-implement the skill's purpose with ad-hoc agents, manual file reads, or improvised workflows. The skill contains tested, structured logic — use it. - Skip complexity classification and routing (step 7) — the user already chose the route.
This is the most common cause of entry sequence bypass: the AI interprets "use X skill" as a goal to achieve creatively rather than as a tool invocation. It is always a tool invocation.
Instruction Priority (highest to lowest)
- Explicit user instructions in the current conversation
- Project-level CLAUDE.md / AGENTS.md
- Superpowers skill instructions
If a user explicitly overrides a skill's behavior, follow the user. Skills are defaults, not mandates.
Core Rule
Before technical execution, select workflow skills explicitly and follow them.
Technical execution includes code edits, debugging, planning, review, test status claims, and branch integration actions.
Entry Sequence
- Invoke
token-efficiencyat session start — applies to all sessions, always. - Fresh project gate — evaluate both conditions in order:
- The user's request contains creation/build intent: any of "build", "create", "make", "implement", "scaffold", "set up", "write", "generate", "develop", "start"
- Run a filesystem check:
ls project-map.md 2>/dev/null— gate only fires if the file does not exist
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 · 192 lines · 122 tokens per session scan A 6ad804f6fc2a
using-superpowers is a skill published in the GitHub repository brunob54/superpowers-orchestrator (3 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 2,723 once invoked, about $0.0006 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
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
privacy-guard
Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-public repo, before…
github-pr-merge
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
assess
Issue triage and status assessment - analyze current state, detect health signals, and recommend next action with full workflow plan.