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 commands/alfredoperez/speckit-companion/superpowers-executegit clone --depth 1 https://github.com/alfredoperez/speckit-companionWhat 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.00017 | $0.00160 |
| Opus 5 | $0.00009 | $0.00080 |
| Sonnet 5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
superpowers-execute 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 yesterday.
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
Take the current GSD phase plan in .planning/ (the most recent *-PLAN.md, or the
phase directory passed as $ARGUMENTS) and hand it to Superpowers:
- Use the writing-plans skill to turn the GSD phase plan into a Superpowers implementation plan.
- Execute that plan with subagent-driven-development: strict TDD, a fresh subagent per task, two-stage review per task.
Do NOT use /gsd-execute-phase — Superpowers is the execution layer in this workflow. When execution finishes, report which plan items are done so /gsd-verify-work can run.
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.
- yesterday First seen · 15 lines · 17 tokens per session scan A 001f275144c7
superpowers-execute is a command published in the GitHub repository alfredoperez/speckit-companion (87 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 160 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 commands, from other repositories
fix-audit
Fix the critical audit vulnerabilities blocking a PR. Usage: /fix-audit.
zooza-setup
One-time Zooza setup — teaches Claude your business vocabulary so it understands your terms in every future session.
example-command
TODO — one-line description shown in the slash-command picker.
commit
Create a conventional commit with emoji prefix.
generate-commit-message-draft
You are a coding assistant operating at the root of a Git repository. Follow the steps below carefully. If any step fails, continue the process and note the reason in the Notes section at the end of the output.
generate-pull-request-draft
You are a member of a software development team. Your task is to create a clear, concise, and professional Pull Request (PR) title and description — step by step, with user confirmation at each stage.