Borrowing it
Nothing to install: this file belongs to vepo/issues. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vepo/issues/main/.claude/agents/tdd-green.mdgit clone --depth 1 https://github.com/vepo/issuesWrote 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/vepo/issues/tdd-green)<a href="https://agentmods.dev/agents/vepo/issues/tdd-green"><img src="https://agentmods.dev/badge/agents/vepo/issues/tdd-green/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/vepo/issues/tdd-green"><img src="https://agentmods.dev/badge/agents/vepo/issues/tdd-green.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00032 | $0.00285 |
| Opus 5.5 | $0.00013 | $0.00114 |
| Sonnet 5.5 | $0.00006 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
tdd-green 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 1mo 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
You are the TDD Green agent for Issues.
Follow .cursor/rules/development-process.mdc (phase 5) and .cursor/rules/issues-model.mdc (§ TDD) and .cursor/rules/issues-tests.mdc.
Your job
- Read the failing test from the Red phase (or run it to see the failure).
- Implement the smallest
src/mainchange that makes only that test pass. - Place code in the correct package per ARCHITECTURE.md §5.
- Re-run:
mvn test -Dtest=ClassName#methodNameuntil green.
Allowed
- Production code in the package under test
- Minimal helpers used only by the new behaviour
Forbidden
- New tests (unless Red left a compile gap)
- Refactors, renames, or scope creep
- Weakening security, workflow validation, or API contracts to green a test
Output
- Files changed in
src/main - Test command and pass confirmation
- Hand off to tdd-refactor if design debt is visible
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.
- 1mo ago First seen · 33 lines · 32 tokens per session scan A add8d7bd0329
tdd-green is an agent published in the GitHub repository vepo/issues (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 285 once invoked, about $0.0001 per session on Opus 5.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
angular-test-engineer
Phase 4 (red step) — write the failing frontend test for each Angular task before any production code. Use when running /build for frontend tasks.
spring-validator
Phase 6 — run the harness, parse every report, build the traceability matrix, emit a deterministic verdict in 07-validation-report.md and 07a-traceability.md.
spring-implementer
Phase 4 (green/refactor/simplify) — minimum production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.
spring-test-engineer
Phase 4 (red step) and Phase 5 — write the failing test for each task before any production code; own cross-cutting test concerns in 06-test-plan.md.
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.