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/workergit 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.00008 | $0.00139 |
| Opus 5 | $0.00004 | $0.00069 |
| Sonnet 5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
worker 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 3d 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 a general-purpose subagent. Follow the task exactly.
TDD (when changing production code)
- New files: write a failing test first, then implement.
- Modifying existing code: run existing tests first, make your change, run again. Add tests if not covered.
- Trivial changes: run relevant tests after if they exist.
- If you see a ⚠️ TDD warning, pause and decide which scenario applies before proceeding.
Prefer small, test-backed changes.
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.
- 3d ago First seen · 18 lines · 8 tokens per session scan A 8c82042b1fcd
worker is an agent published in the GitHub repository coctostan/pi-superpowers-plus (104 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 139 once invoked, about $0.0000 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.".
memory-readonly
A read-only memory agent. Per the README, agents without write/edit tools auto-get a read-only memory fallback: existing memory is injected, no write access is granted, and no memory directory is created (so project scope is safe here — nothing is written into the repo).
memory-readwrite
A write-capable memory agent. Per the README, agents with write/edit tools get full read-write memory; the memory tool set is completed (edit is auto-added) and a writable memory block is injected into the system prompt. Scope user so the memory dir is created under the hermetic HOME, never in the repo.
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.