autonomous-tdd

An automated development workflow that turns a product requirements document into tested code using test-driven development, or TDD. TDD means writing a failing test first, making it pass, and then improving the code.

In plain words
What is it for?
Use it to build working, tested code from a PRD through the red-green-refactor cycle: create a failing test, implement the behavior, and refactor the result.
Why use it?
It structures the path from requirements to implementation and keeps tests involved throughout the work.

Command for Claude Code

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 commands/sam-agents/sam/autonomous-tdd
Clone the repo
git clone --depth 1 https://github.com/sam-agents/sam

Made for: Claude Code.

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 74 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.00029 $0.00074
Opus 5 $0.00015 $0.00037
Sonnet 5 $0.00006 $0.00015
Haiku 4.5 $0.00003 $0.00007

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

Security

Grade A, and why

autonomous-tdd 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.

.claude/commands/sam/core/workflows/autonomous-tdd.md · 7 lines

What it actually says

IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_sam/core/workflows/autonomous-tdd/workflow.md, READ its entire contents and follow its directions exactly!

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. 2d ago First seen · 7 lines · 29 tokens per session scan A 8966e1da0aa0

Subscribe to this mod's changes

autonomous-tdd is a command published in the GitHub repository sam-agents/sam (18 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 74 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.