tdd-guide

tdd-guide is an agent for Claude Code from vibeeval/vibecosystem. It costs 42 tokens per session (1,884 once invoked), scanned A, original, MIT.

A Test-Driven Development specialist that guides developers to write a failing test before implementing the code. TDD follows a repeatable red-green-refactor cycle: fail, make it pass, then improve the design.

In plain words
What is it for?
Use it when adding features, fixing bugs, or refactoring to plan unit, integration, and end-to-end tests and work test-first.
Why use it?
It catches expected edge cases early and keeps new code tied to explicit behaviour. It also reduces the risk of breaking existing behaviour during fixes or refactoring.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

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/vibeeval/vibecosystem/tdd-guide
Clone the repo
git clone --depth 1 https://github.com/vibeeval/vibecosystem

Made for: Claude Code.

Wrote 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.

agentmods badge for tdd-guide

README.md
[![agentmods](https://agentmods.dev/badge/agents/vibeeval/vibecosystem/tdd-guide.svg)](https://agentmods.dev/agents/vibeeval/vibecosystem/tdd-guide)
Your own site
<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/tdd-guide"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/tdd-guide.svg" alt="Measured on agentmods" height="20"></a>
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,884 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.1 $0.00042 $0.01884
Opus 5 $0.00021 $0.00942
Sonnet 5 $0.00008 $0.00377
Haiku 4.5 $0.00004 $0.00188

Measured 2d ago against content hash 0e968334accf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 · 288 lines

How it starts

The opening of the file, as written. The whole thing — 288 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 · 288 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 · 288 lines · 42 tokens per session scan A 0e968334accf

Subscribe to this mod's changes

tdd-guide is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 28d ago), licensed MIT. It adds 42 tokens to every session and 1,884 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-09-03.

Related

Other agents, from other repositories

tdd-guide

Red-Green-Refactor TDD 사이클 강제. 테스트 먼저 작성 → 최소 코드 구현 → 리팩토링. 커버리지 80%+ 엣지 케이스 분석 포함. Use proactively when 새 기능 구현, 버그 수정, 리팩토링을 시작할 때 — 특히 "TDD로", "테스트 먼저", "테스트 작성"이 포함된 요청. 빌드 에러 수정은 build-error-resolver, E2E는 e2e-runner 사용.

sangrokjung/claude-forge · 110 tokens

tdd-guide

Enforces test-first development through the RED-GREEN-IMPROVE cycle. Use when writing new features or fixing bugs.

mshadmanrahman/pm-pilot · 29 tokens

shipyard-disciplined-builder

TDD-disciplined implementer for one Shipyard feature task in an isolated worktree. Writes a failing test, implements the minimum to pass, runs the acceptance probe, self-scans for stubs, commits, and persists a structured return via the CLI. Dispatched by the dispatching-task-loop capability skill with a brief…

Acendas/shipyard · 105 tokens

grid-tester

Use this agent for test strategy, TDD workflows, integration/e2e coverage, and flaky test hardening. Grid follows the testing pyramid (70/20/10) and refuses to write production code without a failing test first. Examples: user: "add tests for the auth refactor" assistant: "I will use Grid to write tests following the…

evolution-foundation/evo-nexus · 166 tokens

tdd-guide

Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.

YousefNabil-SOC/claude-apex · 42 tokens

implementor

End-to-end feature implementation with TDD discipline.

namastexlabs/automagik-tools · 12 tokens