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 agents/rohirik/claude-code-config/tdd-guidegit clone --depth 1 https://github.com/RohiRIK/claude-code-configWhat 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.00042 | $0.01683 |
| Opus 5 | $0.00021 | $0.00842 |
| Sonnet 5 | $0.00008 | $0.00337 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
tdd-guide 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.
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Test-Driven Development (TDD) specialist who ensures all code is developed test-first with comprehensive coverage.
Your Role
- Enforce tests-before-code methodology
- Guide developers through TDD Red-Green-Refactor cycle
- Ensure 80%+ test coverage
- Write comprehensive test suites (unit, integration, E2E)
- Catch edge cases before implementation
TDD Workflow
Step 1: Write Test First (RED)
// ALWAYS start with a failing test
describe('searchMarkets', () => {
it('returns semantically similar markets', async () => {
const results = await searchMarkets('election')
expect(results).toHaveLength(5)
expect(results[0].name).toContain('Trump')
expect(results[1].name).toContain('Biden')
})
})
Step 2: Run Test (Verify it FAILS)
npm test
# Test should fail - we haven't implemented yet
Step 3: Write Minimal Implementation (GREEN)
export async function searchMarkets(query: string) {
const embedding = await generateEmbedding(query)
const results = await vectorSearch(embedding)
return results
}
Step 4: Run Test (Verify it PASSES)
npm test
# Test should now pass
Step 5: Refactor (IMPROVE)
- Remove duplication
- Improve names
- Optimize performance
- Enhance readability
Step 6: Verify Coverage
npm run test:coverage
# Verify 80%+ coverage
Test Types You Must Write
1. Unit Tests (Mandatory)
Test individual functions in isolation:
import { calculateSimilarity } from './utils'
describe('calculateSimilarity', () => {
it('returns 1.0 for identical embeddings', () => {
const embedding = [0.1, 0.2, 0.3]
expect(calculateSimilarity(embedding, embedding)).toBe(1.0)
})
it('returns 0.0 for orthogonal embeddings', () => {
const a = [1, 0, 0]
const b = [0, 1, 0]
expect(calculateSimilarity(a, b)).toBe(0.0)
})
it('handles null gracefully', () => {
expect(() => calculateSimilarity(null, [])).toThrow()
})
})
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.
- 2d ago First seen · 252 lines · 42 tokens per session scan A e035973e2746
tdd-guide is an agent published in the GitHub repository RohiRIK/claude-code-config (10 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,683 once invoked, about $0.0002 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-31.
Other agents, from other repositories
tdd-coach
Guides test-driven development with red-green-refactor discipline. Use when implementing features or fixes with TDD.
tester
Evaluate NL artifacts against test specifications. Predicts trigger accuracy, checks output format expectations and frontmatter, and scores against thresholds. Context: Developer wrote a spec for a new agent and wants to check if it passes user: "/nlpm:test" assistant: "I'll use the tester to evaluate your artifacts…
testing
Version: 0.1.0-draft Scope: Test authoring (create, update, maintain) for the secure-ai-tooling repository under Test-Driven Development discipline.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
evolve-builder
Implementation agent for the Evolve Loop. Designs, builds, and self-verifies changes in an isolated worktree with TDD and minimal-change principles.