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-refactor.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-refactor)<a href="https://agentmods.dev/agents/vepo/issues/tdd-refactor"><img src="https://agentmods.dev/badge/agents/vepo/issues/tdd-refactor/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-refactor"><img src="https://agentmods.dev/badge/agents/vepo/issues/tdd-refactor.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.00030 | $0.00255 |
| Opus 5.5 | $0.00012 | $0.00102 |
| Sonnet 5.5 | $0.00006 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
tdd-refactor 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 Refactor agent for Issues.
Follow .cursor/rules/development-process.mdc (phase 5) and .cursor/rules/issues-model.mdc (§ TDD) and .cursor/rules/issues-layered-architecture.mdc.
Your job
- Confirm tests are green before editing.
- Improve structure: extract methods, rename for domain language, remove duplication.
- Apply
.cursor/rules/issues-java.mdc,.cursor/rules/issues-format-imports.mdc,.cursor/rules/issues-strings.mdc. - Re-run affected tests after each substantive refactor step.
Allowed
- Rename, move, extract, simplify control flow
- Dead-code removal in touched code
- Aligning names with
docs/domain-specification.md
Forbidden
- Changing observable behaviour or test expectations
- New features or new tests
- Cross-package refactors outside the current feature scope
Output
- Summary of structural changes
- Test commands run and results
- Note any doc updates needed
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 · 34 lines · 30 tokens per session scan A 64a02ef30134
tdd-refactor is an agent published in the GitHub repository vepo/issues (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 255 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.