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 skills add coctostan/pi-superpowers-plus --skill test-driven-developmentgit clone --depth 1 https://github.com/coctostan/pi-superpowers-plusWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/coctostan/pi-superpowers-plus/test-driven-development)<a href="https://agentmods.dev/skills/coctostan/pi-superpowers-plus/test-driven-development"><img src="https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/test-driven-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/coctostan/pi-superpowers-plus/test-driven-development"><img src="https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/test-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00017 | $0.01950 |
| Opus 5.5 | $0.00007 | $0.00780 |
| Sonnet 5.5 | $0.00003 | $0.00390 |
| Haiku 4.5 | $0.00002 | $0.00195 |
Grade A, and why
test-driven-development 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 1mo 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Related skills: Before claiming done, use
/skill:verification-before-completionto verify tests actually pass.
Test-Driven Development (TDD)
Overview
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
Violating the letter of the rules is violating the spirit of the rules.
Prerequisites
- Active branch (not main) or user-confirmed intent to work on main
- Approved plan or clear task scope
When to Use — Three Scenarios
Not every change requires the same TDD approach. Determine which scenario applies:
Scenario 1: New Feature / New File
Full TDD cycle. No shortcuts.
- Write a failing test
- Watch it fail
- Write minimal code to pass
- Watch it pass
- Refactor
- Repeat
This is the default. If in doubt, use this scenario.
Scenario 2: Modifying Code with Existing Tests
When changing code that already has test coverage:
- Run existing tests — confirm green
- Make your change
- Run tests again — confirm still green
- If your change isn't covered by existing tests, add a test for it
- If existing tests already cover the changed behavior, you're done
Key: You must verify existing tests pass before and after your change. If you can't confirm test coverage, fall back to Scenario 1.
Scenario 3: Trivial Change
For typo fixes, config tweaks, string changes, renames:
- Use judgment
- If relevant tests exist, run them after your change
- Don't write a new test for a string literal change
Be honest: If the change touches logic, it's not trivial. Use Scenario 1 or 2.
Interpreting Runtime Warnings
The workflow monitor tracks your TDD phase and may inject warnings like:
⚠️ TDD: Writing source code (src/foo.ts) without a failing test.
When you see this, pause and assess:
- Which scenario applies to this change?
- If Scenario 2: run existing tests to confirm coverage, then proceed
- If Scenario 1: write a failing test first
- If Scenario 3: proceed, run tests after
What ships with it
4 files 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.
- 1mo ago First seen · 256 lines · 17 tokens per session scan A f0bb91194955
test-driven-development is a skill published in the GitHub repository coctostan/pi-superpowers-plus (106 stars, last pushed 8mo ago), licensed MIT. It adds 17 tokens to every session and 1,950 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
portfolio-fixture
The zero-judgement test of the portfolio flow. Copies a fixed plan to the outbox and reports it.
xcodebuildmcp
Build/test Xcode projects via the XcodeBuildMCP MCP server using a local CLI wrapper for pi (no MCP support). Use when the user mentions Xcode, xcodebuild, iOS builds/tests, or XcodeBuildMCP.
agent-test-generator
Specialist subagent: Generates comprehensive test suites using TDD patterns. Use only when the user explicitly asks for tests, improved coverage, or test-first development.
testing
TDD/BDD testing principles. Use when writing tests, reviewing test coverage, setting up testing, or discussing test strategy and test architecture.
refactor-ops
Safe refactoring patterns - extract, rename, restructure with test-driven methodology and dead code detection. Use for: refactor, refactoring, extract function, extract component, rename, move file, restructure, dead code, unused imports, code smell, duplicate code, long function, god object, feature envy, DRY…
testing-ops
Cross-language testing strategies and patterns. Triggers on: test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation.