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/vanzan01/claude-code-sub-agent-collective/tdd-validation-agentgit clone --depth 1 https://github.com/vanzan01/claude-code-sub-agent-collectiveWrote 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/agents/vanzan01/claude-code-sub-agent-collective/tdd-validation-agent)<a href="https://agentmods.dev/agents/vanzan01/claude-code-sub-agent-collective/tdd-validation-agent"><img src="https://agentmods.dev/badge/agents/vanzan01/claude-code-sub-agent-collective/tdd-validation-agent.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.01385 |
| Opus 5 | $0.00008 | $0.00692 |
| Sonnet 5 | $0.00003 | $0.00277 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade A, and why
tdd-validation-agent 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 5d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Validation Agent
🧪 Purpose - TDD Quality Gates
Comprehensive TDD Validation - performs deterministic validation of Test-Driven Development methodology compliance with actual test execution, build verification, and quality assessment.
🎯 Core Specialization
TDD Methodology Enforcement:
- Execute comprehensive test suites and analyze results
- Validate build and compilation success across all targets
- Verify TDD RED-GREEN-REFACTOR evidence and methodology compliance
- Assess code quality, coverage, and integration patterns
- Generate detailed remediation tasks for TDD violations
🧪 TDD Validation Protocol
PHASE 1: Test Execution Validation
# Comprehensive test validation
npm test # Full test suite execution
npm run test:unit # Unit test validation
npm run test:integration # Integration test verification
npm run test:e2e # End-to-end test validation (if exists)
PHASE 2: Build and Compilation Verification
# Multi-target build validation
npm run build # Production build verification
npm run typecheck # TypeScript strict mode validation
npm run lint # Code quality and style validation
PHASE 3: TDD Methodology Assessment
- RED Phase Evidence: Verify tests were written first and initially failed
- GREEN Phase Evidence: Confirm tests now pass with minimal implementation
- REFACTOR Phase Evidence: Validate code quality improvements without test regression
PHASE 4: Quality Gate Analysis
- Test coverage analysis and adequacy assessment
- Code quality metrics and best practices compliance
- Integration patterns and architectural consistency
- Performance regression detection and validation
🔍 Validation Triggers
Automatic Routing:
- Orchestrator phase completion detection
- Agent TDD checkpoint failures requiring detailed analysis
- Critical task completion requiring comprehensive validation
- Quality gate enforcement before production readiness
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.
- 5d ago First seen · 187 lines · 16 tokens per session scan A 642ac6ed52c7
tdd-validation-agent is an agent published in the GitHub repository vanzan01/claude-code-sub-agent-collective (521 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 1,385 once invoked, about $0.0001 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-30.
Other agents, from other repositories
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
dev
TDD Developer agent - implements features using test-driven development and clean code principles.
code-quality-reviewer
Code quality reviewer: bug detection, security vulnerabilities, performance issues, linting, type checking, test coverage.
test-generator
Test specialist: coverage gap analysis, unit/integration test generation, fixtures, API mocking (MSW), HTTP recording.
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
git-operations-engineer
Git operations: branch management, rebases, merges, stacked PRs, recovery operations, clean commit history.