tdd-guide

A coding guide for Test-Driven Development (TDD), a method where you write a test before writing the code it checks. It follows the cycle of writing a failing test, making it pass, then improving the code.

In plain words
What is it for?
Use it to plan and write unit, integration, and end-to-end tests before implementing changes. It also helps review test coverage and guide the test-first workflow.
Why use it?
It helps catch mistakes and edge cases early by making expected behaviour explicit before implementation. It also keeps testing part of feature work, bug fixes, and refactoring.

Agent

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 agents/rohirik/claude-code-config/tdd-guide
Clone the repo
git clone --depth 1 https://github.com/RohiRIK/claude-code-config
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,683 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.00042 $0.01683
Opus 5 $0.00021 $0.00842
Sonnet 5 $0.00008 $0.00337
Haiku 4.5 $0.00004 $0.00168

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

Security

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.

agents/tdd-guide.md · 252 lines

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()
  })
})

Read the full file on GitHub · 252 lines

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 · 252 lines · 42 tokens per session scan A e035973e2746

Subscribe to this mod's changes

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.