test-driven-development

test-driven-development is a skill for Claude Code, Codex from DollarDill/beads-superpowers. It costs 17 tokens per session (2,514 once invoked), scanned A, original, MIT.

A development workflow called test-driven development, or TDD, where a developer writes a test first, confirms that it fails, then writes the smallest code needed to pass it.

In plain words
What is it for?
Use it for new features, bug fixes, refactoring, and other behaviour changes, beginning from an approved specification or plan.
Why use it?
It helps verify that tests check the intended behaviour and keeps implementation tied to expected results.

Skill for Claude CodeCodex

Part of the beads-superpowers plugin — 22 skills, 1 agent, 1 hook shipped together

Install

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.

agentmods
npx agentmods add skills/dollardill/beads-superpowers/test-driven-development
Any agent
npx skills add DollarDill/beads-superpowers --skill test-driven-development
Clone the repo
git clone --depth 1 https://github.com/DollarDill/beads-superpowers

Made for: Claude Code, Codex.

Or install beads-superpowers, the plugin that ships this one along with the rest of its 22 skills, 1 agent, 1 hook.

Wrote 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.

agentmods badge for test-driven-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/dollardill/beads-superpowers/test-driven-development.svg)](https://agentmods.dev/skills/dollardill/beads-superpowers/test-driven-development)
Your own site
<a href="https://agentmods.dev/skills/dollardill/beads-superpowers/test-driven-development"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/test-driven-development.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,514 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.02514
Opus 5 $0.00009 $0.01257
Sonnet 5 $0.00003 $0.00503
Haiku 4.5 $0.00002 $0.00251

Measured 4d ago against content hash 4367c0a8365e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 4d 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.

skills/test-driven-development/SKILL.md · 343 lines

How it starts

The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Spec-backed: implementation starts from an approved spec or plan. Before the first edit, state the file you are working from — Working from: <spec-or-plan path>. No such file yet? Say so and run brainstorming first. A plan task, a completed root-cause investigation, or a typo/comment/rename already satisfies this.

When to Use

Always:

  • New features
  • Bug fixes
  • Refactoring
  • Behavior changes

Exceptions (ask your human partner):

  • Throwaway prototypes
  • Generated code
  • Configuration files

Thinking "skip TDD just this once"? Stop. That's rationalization.

The Iron Law

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

Write code before the test? Delete it. Start over.

TDD's Iron Law is one instance of the Production-Grade Doctrine — the no-shortcuts posture applied to tests.

No exceptions:

  • Don't keep it as "reference"
  • Don't "adapt" it while writing tests
  • Don't look at it
  • Delete means delete

Implement fresh from tests. Period.

Red-Green-Refactor

digraph tdd_cycle {
    rankdir=LR;
    red [label="RED\nWrite failing test", shape=box, style=filled, fillcolor="#ffcccc"];
    verify_red [label="Verify fails\ncorrectly", shape=diamond];
    green [label="GREEN\nMinimal code", shape=box, style=filled, fillcolor="#ccffcc"];
    verify_green [label="Verify passes\nAll green", shape=diamond];
    refactor [label="REFACTOR\nClean up", shape=box, style=filled, fillcolor="#ccccff"];
    next [label="Next", shape=ellipse];

    red -> verify_red;
    verify_red -> green [label="yes"];
    verify_red -> red [label="wrong\nfailure"];
    green -> verify_green;
    verify_green -> refactor [label="yes"];
    verify_green -> green [label="no"];
    refactor -> verify_green [label="stay\ngreen"];
    verify_green -> next;
    next -> red;
}

Read the full file on GitHub · 343 lines

Files

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.

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.

  1. 4d ago First seen · 343 lines · 17 tokens per session scan A 4367c0a8365e

Subscribe to this mod's changes

test-driven-development is a skill published in the GitHub repository DollarDill/beads-superpowers (26 stars, last pushed 13d ago), licensed MIT. It adds 17 tokens to every session and 2,514 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.

Related

Other skills, from other repositories

workflows-driven-development

Dynamic build workflow: plans a goal into tasks, builds each test-first, and reviews every step.

7xuanlu/ultrapowers · 25 tokens

test-driven-development-codex

Enforce strict test-driven development via Codex-backed implementation. Use only when the user explicitly asks for the Codex-backed TDD workflow.

mzored/superpowers-cc-to-codex · 35 tokens

beads-onboard

This skill should be used when the user asks to "onboard beads", "set up beads conventions", "configure beads for this project", "set up project labels", "improve my beads quality", "run beads onboard", "upgrade beads conventions", "re-run beads onboard", or when a project has .beads/ but no .beads/conventions/…

seanmartinsmith/sms-public-mkt · 96 tokens

tdd

Guides test-driven development — decomposes a feature or bug fix into testable behaviors, then runs Red-Green-Refactor cycles with a failing test before every implementation. Auto-detects specs from docs/specs/ or docs/jira/, creates a feature branch (optional worktree), commits per cycle, and pushes. Recommends…

oprogramadorreal/optimus-claude · 90 tokens

auto-loop

TDD-based autonomous development loop with checkpoint recovery and observability changelog.

claude-world/director-mode-lite · 17 tokens

workflow

Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.

claude-world/director-mode-lite · 52 tokens