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/procoders/superpowers-v/v-initgit clone --depth 1 https://github.com/procoders/superpowers-vWhat 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.00046 | $0.12926 |
| Opus 5 | $0.00023 | $0.06463 |
| Sonnet 5 | $0.00009 | $0.02585 |
| Haiku 4.5 | $0.00005 | $0.01293 |
Grade A, and why
v-init 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 2d 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 — 804 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /v:init — the Compound V capability + stance setup for this
project. Argument (optional): {{args}} may name a stance to pre-select
(balanced | conservative | cost-aware | claude-only); otherwise you recommend one.
This walkthrough IS the configurator. There is no separate shipped playground or
runtime UI — the stance is set here and in routing-policy.md.
A standalone HTML configurator, if it exists, is only an optional dev tool, never a
shipped surface. Do not claim otherwise.
Run the steps in order. Do not batch installs — detect everything first, then walk the user through missing pieces one at a time, confirming after each.
Step 1 — Detect capabilities
Probe each, and remember the result. Do not install anything yet.
1a. Codex CLI (and verify the EXEC flag surface)
command -v codex
If absent → Codex is not available (record it; routing will be Claude-only).
If present, verify the flags Compound V depends on live in the codex exec
subcommand help — not merely in the merged top-level help. This is the check that
caught the real adapter bug (PRD §3): --ask-for-approval appears in codex --help
but is absent from codex exec --help, because it is a top-level/interactive flag.
Asserting against the wrong help would have shipped an adapter that fails on every job.
# Assert the worker flags are in the EXEC subcommand help specifically:
codex exec --help 2>/dev/null | grep -q -- '--cd' || echo "MISSING --cd in exec help"
codex exec --help 2>/dev/null | grep -q -- '--sandbox' || echo "MISSING --sandbox in exec help"
codex exec --help 2>/dev/null | grep -q -- '--skip-git-repo-check' || echo "MISSING --skip-git-repo-check in exec help"
codex exec --help 2>/dev/null | grep -q -- '--model' || echo "MISSING --model in exec help"
codex exec --help 2>/dev/null | grep -q -- '--output-last-message' || echo "MISSING --output-last-message in exec help"
# And confirm the bug-marker flag is NOT in exec help (it must be top-level only):
if codex exec --help 2>/dev/null | grep -q -- '--ask-for-approval'; then
echo "WARN: --ask-for-approval appears in exec help on this codex version — re-check the adapter"
fi
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.
- 2d ago First seen · 804 lines · 46 tokens per session scan A 3db1849d6ebe
v-init is a command published in the GitHub repository procoders/superpowers-v (35 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 12,926 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-08-30.
Other commands, from other repositories
deepen
Spare-budget design pass. Make one shallow module deep — smaller interface, behavior held, tests green before & after.
research
Gather external knowledge into §R so build grounds in facts, not hallucinations. Every finding cites a source.
review
Adversarial senior review of the spec before build. Refute, don't rubber-stamp. Ends in a go/no-go gate.
build
Plan-then-execute against SPEC.md. Native Claude Code loop, no sub-agents.
check
Drift detector. Diff SPEC.md against code. Read-only, zero writes.
full_cycle
Interactive workflow to execute the entire development cycle from brainstorming to the integration decision.