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 commands/cassler/awesome-claude-code-setup/tddgit clone --depth 1 https://github.com/cassler/awesome-claude-code-setupWhat 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.00000 | $0.00425 |
| Opus 5 | $0.00000 | $0.00212 |
| Sonnet 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 3d 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.
- 3d 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 (267 stars, last pushed 4mo 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
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
go-test
Go TDD workflow with table-driven tests.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化（設計レビュー→作業計画→TDD実装）.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
execute-plan
Execute an implementation plan methodically with TDD and continuous validation.
tdd
强制执行测试驱动开发工作流。首先搭建接口，生成测试，然后从实现能通过测试的最小代码。确保 80%+ 的覆盖率。.