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.
git clone --depth 1 https://github.com/cassler/awesome-claude-code-setupWrote 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/commands/cassler/awesome-claude-code-setup/tdd)<a href="https://agentmods.dev/commands/cassler/awesome-claude-code-setup/tdd"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/tdd/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/commands/cassler/awesome-claude-code-setup/tdd"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/tdd.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.00000 | $0.00425 |
| Opus 5.5 | $0.00000 | $0.00170 |
| Sonnet 5.5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
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 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.
What it actually says
Test-Driven Development (TDD) Workflow
I'll help you implement changes using Test-Driven Development. This is an Anthropic-favorite workflow that ensures high-quality, well-tested code.
TDD Process Overview
I'll follow these steps strictly:
- Write failing tests first - Based on your requirements
- Verify tests fail - Confirm we're testing the right thing
- Implement minimal code - Just enough to make tests pass
- Refactor if needed - Improve code while keeping tests green
Your Requirements
Please provide:
-
What feature/change do you want?
- Describe the expected behavior
- Include any edge cases to handle
-
Test examples (optional but helpful):
- Input/output pairs
- Error scenarios
- Performance requirements
-
Test framework preferences:
- Which testing framework does your project use?
- Any specific test patterns to follow?
Important Notes
- I will NOT write any implementation code until tests are written and failing
- I will NOT modify tests once we start implementation (unless there's a bug in the test itself)
- I will use your project's test commands to run tests efficiently
- I'll identify the appropriate test command from your project setup
Process I'll Follow
Phase 1: Test Creation
# 1. Analyze existing test structure
chs find-file "*.test.*"
chs find-file "*.spec.*"
# 2. Write comprehensive tests
# 3. Run tests and confirm they fail
Phase 2: Implementation
# 1. Write minimal implementation
# 2. Run tests repeatedly until all pass
# 3. Avoid overfitting to specific test cases
Phase 3: Verification
# 1. Run full test suite
# 2. Check test coverage if available
# 3. Commit when all tests pass
Let's begin! What would you like to implement using TDD?
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 · 62 lines · 0 tokens per session scan A 84f6257b2f45
tdd is a command published in the GitHub repository cassler/awesome-claude-code-setup (268 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 425 tokens. 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 commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.