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 skills/oleg494/coding-kit/superpowersnpx skills add oleg494/coding-kit --skill superpowersgit clone --depth 1 https://github.com/oleg494/coding-kitWhat 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.00070 | $0.00771 |
| Opus 5 | $0.00035 | $0.00385 |
| Sonnet 5 | $0.00014 | $0.00154 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Superpowers — main development method
Always-on skill. Every non-trivial task goes through 5 phases.
The Cycle
PLAN ──→ TDD ──→ IMPLEMENT ──→ VERIFY ──→ REPORT
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
Spec Red test Green code Evidence Outcome
first first minimal observed first
Phase skills (obra accretion)
Kit v2: each phase has a granular skill helper. A phase is not replaced, but deepened:
- PLAN →
brainstorming(design questions, spec),writing-plans(execution plan) - IMPLEMENT →
dispatching-parallel-agents(parallel slices), per-plan implementation with checkpoints - VERIFY →
verification-before-completion(fresh output),requesting-code-review,fable-judge(adversarial) - Debug →
systematic-debugging - Git →
using-git-worktrees,finishing-a-development-branch
Phase 1: PLAN
Formulate what "done" means — concrete, observable.
- What should be true when the task is done?
- Which files do you touch? Which do you NOT touch?
- What assumptions do you make?
- Complex task (>3 files / >5 changes) → split into atomic tasks.
Scope discipline: touch only what the task requires. Not "I'll clean up along the way".
Phase 2: TDD
Red test → green code → refactoring.
- No code without a failing test.
- Test = spec. Test name = rule:
test_payment_idempotent,test_referral_no_self. - A test verifies behavior, not implementation.
Prove-It Pattern (bug fix)
Bug report → test reproducing the bug → test FAILS → fix → test GREEN
Phase 3: IMPLEMENT
Minimal change that makes the test green.
- YAGNI: don't add anything beyond what the test requires.
- Style — as in the surrounding code. Don't refactor someone else's code without asking.
- DRY: duplicated in 3+ places? → shared source.
Phase 4: VERIFY
Evidence, not inference.
- Test green? → observed.
- All existing tests green? → ran.
- Build not broken? → checked.
- Linter clean? → ran.
- Bug fix → TWINS: searched for the same pattern in the codebase.
- No "seems to work" — only "observed that it works".
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 92 lines · 70 tokens per session scan A 7e80bff52f6a
superpowers is a skill published in the GitHub repository oleg494/coding-kit (1 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 771 once invoked, about $0.0003 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
run
Execute a named agent role with optimized instructions. Explicit invocation only ($run). Never trigger implicitly.
tip
Deliver a transformative life perspective shift and a productivity tip. Use when the user invokes /tip or wants non-technical inspiration or a fresh mental model.
agentic-security-review
Run a security and dependency audit for agent systems, tool-using AI apps, MCP/A2A integrations, or security-sensitive AI-generated code. Check slopsquatting risk, tool shadowing, rug pulls, memory/context poisoning, secrets, unsafe permissions, and common CWE patterns. Use when asked for security review, dependency…
agentic-spec
Create a structured specification before agentic coding work. Assemble the six context types, scale rigor for prototype/internal/production tasks, produce SPEC.md, and configure focused AGENTS.md boundaries. Use when asked to write a spec, plan a feature, design an agent/system, define architecture, or create…
agentic-evals
Design evaluation contracts and test plans for agentic systems. Create deterministic tests, trajectory evals, quality dimensions, gold-set criteria, and CI gates before or after implementation. Use when asked for tests first, an eval plan, success criteria, non-deterministic testing, LLM-as-judge setup, or…
agentic-production-readiness
Prepare an AI agent system for production operation. Cover SHIELD controls, sandbox/canary/production rollout, OpenTelemetry observability with GenAI semantic conventions, Agent Card drafting, governance, and post-deploy monitoring. Use for production readiness checks, go-live checklists, agent monitoring, agent…