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.
git clone --depth 1 https://github.com/hculap/better-codeWrote 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/commands/hculap/better-code/tdd-refactor)<a href="https://agentmods.dev/commands/hculap/better-code/tdd-refactor"><img src="https://agentmods.dev/badge/commands/hculap/better-code/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/commands/hculap/better-code/tdd-refactor"><img src="https://agentmods.dev/badge/commands/hculap/better-code/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.00007 | $0.01540 |
| Opus 5.5 | $0.00003 | $0.00616 |
| Sonnet 5.5 | $0.00001 | $0.00308 |
| Haiku 4.5 | $0.00001 | $0.00154 |
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 8d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Safe Refactor
Perform safe refactoring protected by existing tests: $ARGUMENTS
Parse Arguments
Extract from arguments:
- Target: What to refactor (required) - can be:
- File path:
src/utils.ts - Symbol name:
calculateTotal - Description:
extract validation logic
- File path:
- --strict / --standard / --relaxed: Override strictness mode (optional)
- --file : Target specific file (optional, overrides target parsing)
- --plan: Force planning mode (require approval before refactoring)
- --skip-plan: Skip planning entirely, execute directly
Target Resolution
Resolve the refactor target:
-
If looks like a file path (contains
/or.):- Treat as file path
- Verify file exists
- Load file for analysis
-
If looks like a symbol (single word, camelCase, PascalCase):
- Search codebase for function/class/method with that name
- If found: Target that symbol
- If multiple matches: Ask user to clarify
-
If descriptive text:
- Analyze description to identify target code
- Search for relevant patterns
- Confirm understanding with user
Plan Mode Decision
Determine planning behavior based on flags:
- If
--skip-planflag: Skip planning, proceed directly to refactoring - If
--planflag: Force planning before refactoring - If neither flag (default): Ask user using AskUserQuestion:
- "Would you like to review and approve the refactoring plan before I start?"
- Options: "Yes, show me the plan" / "No, proceed directly"
Refactoring Planning Phase (unless --skip-plan)
If planning is enabled (via --plan flag or user choice):
- Enter plan mode: Use EnterPlanMode tool
- Analyze the target code:
- What code smells or issues exist?
- What refactoring transformations apply?
- What tests cover this code?
- Write refactoring plan to plan file including:
- Target files and symbols
- Proposed refactoring steps (in order)
- Expected benefits of each change
- Relevant test coverage
- Exit plan mode: Wait for user approval via ExitPlanMode
- Proceed to refactoring only after approval
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.
- 8d ago Changed · +7 tokens per session 29db423f10e8
- 1mo ago First seen · 253 lines · 0 tokens per session scan A b51c161530ab
tdd-refactor is a command published in the GitHub repository hculap/better-code (2 stars, last pushed 8d ago), licensed MIT. It adds 7 tokens to every session and 1,540 once invoked, about $0.0000 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 commands, from other repositories
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
fix
Correction automatisee des bugs identifies par la QA Recette.
tdd
Correction de Bug en Mode TDD/BDD.
forge
/forge Full Forge pipeline (semi-auto + parallel) /forge [prd-file] Forge a specific PRD /forge --blitz Forge with TDD enforcement.
refactor
You are the Refactor Specialist, a rigorous code quality engineer who improves code structure, maintainability, and performance while preserving behavior. You never break working code - you make it better.
blitz
/blitz is a thin alias for /go --mode=semi-auto --parallel --tdd. It runs the full /go pipeline at maximum speed: semi-auto remediation + parallel wave execution + TDD enforcement. Blitz is for well-defined PRDs with independent stories.