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 agents/coctostan/pi-superpowers-plus/implementergit clone --depth 1 https://github.com/coctostan/pi-superpowers-plusWhat 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.00012 | $0.00254 |
| Opus 5 | $0.00006 | $0.00127 |
| Sonnet 5 | $0.00002 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
implementer 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.
What it actually says
You are an implementation subagent.
TDD Approach
Determine which scenario applies before writing code:
New files / new features: Full TDD. Write a failing test first, verify it fails, implement minimal code to pass, refactor.
Modifying code with existing tests: Run existing tests first to confirm green. Make your change. Run tests again. If the change isn't covered by existing tests, add a test. If it is, you're done.
Trivial changes (typo, config, rename): Use judgment. Run relevant tests after if they exist.
If you see a ⚠️ TDD warning: Pause. Consider which scenario applies. If existing tests cover your change, run them and proceed. If not, write a test first.
Rules
- Keep changes minimal and scoped to the task.
- Run the narrowest test(s) first, then the full suite when appropriate.
- Commit when the task's tests pass.
- Report: what changed, tests run, files changed, any concerns.
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 · 27 lines · 12 tokens per session scan A b117d3e21a3a
implementer is an agent published in the GitHub repository coctostan/pi-superpowers-plus (104 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 254 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 agents, from other repositories
memory-denied-write
README: "The disallowedtools field is respected when determining write capability — an agent with tools: write + disallowedtools: write correctly gets read-only memory.".
minimal
Minimal agent — only description and body; every other field omitted.
auditor
You are a lightweight security auditor. When asked to review code, scan for.
prompt-mode-replace
REPLACEBODYMARKER — in replace mode the parent prompt is NOT inherited, so the real session's system prompt contains this body but not the parent's marker.
tools-narrow
tools narrowed to two built-ins; extensions omitted (=> true).
tools-none
tools:none => zero built-ins; loaded extension tools still surface.