agentmods.dev

tdd-refactor

A refactoring command that uses existing tests to check whether code changes remain safe. TDD, or test-driven development, is an approach that uses automated tests to guide code changes.

In plain words
What is it for?
Use it to refactor a file, function, class, or described piece of code, with optional planning and strictness settings.
Why use it?
It reduces the chance that reorganizing code will change its behavior or introduce regressions.

Command

2 7mo ago A scan 7 tokens original MIT
View the source file hculap/better-code
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 commands/hculap/better-code/tdd-refactor
Clone the repo
git clone --depth 1 https://github.com/hculap/better-code
Per session 7 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,539 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 $0.00007 $0.01539
Opus 5 $0.00003 $0.00770
Sonnet 5 $0.00001 $0.00308
Haiku 4.5 $0.00001 $0.00154

Measured yesterday against content hash b51c161530ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

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.

plugins/tdd-dev/commands/tdd-refactor.md · 253 lines

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
  • --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:

  1. If looks like a file path (contains / or .):

    • Treat as file path
    • Verify file exists
    • Load file for analysis

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

  3. 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:

  1. If --skip-plan flag: Skip planning, proceed directly to refactoring
  2. If --plan flag: Force planning before refactoring
  3. 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):

  1. Enter plan mode: Use EnterPlanMode tool
  2. Analyze the target code:
    • What code smells or issues exist?
    • What refactoring transformations apply?
    • What tests cover this code?
  3. Write refactoring plan to plan file including:
    • Target files and symbols
    • Proposed refactoring steps (in order)
    • Expected benefits of each change
    • Relevant test coverage
  4. Exit plan mode: Wait for user approval via ExitPlanMode
  5. Proceed to refactoring only after approval

Read the full file on GitHub · 253 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. yesterday First seen · 253 lines · 0 tokens per session scan A b51c161530ab

Subscribe to this mod's changes

tdd-refactor is a command published in the GitHub repository hculap/better-code (2 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 1,539 once invoked, about $0.0000 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-31.

Code reviewTestingWriting and docsai-toolsclaude-codecode-qualitydev-toolsdocumentationplugins
Related

Other commands, from other repositories

create-skill

Create an AI skill from any source (URL, repo, PDF, video, notebook, etc.).

yusufkaraaslan/Skill_Seekers · 20 tokens

sync-config

Sync a scraping config's URLs against the live documentation site.

yusufkaraaslan/Skill_Seekers · 11 tokens

create_plan

Create detailed implementation plans through interactive research and iteration.

hoblin/claude-ruby-marketplace · 9 tokens

review-pr

Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.

hoblin/claude-ruby-marketplace · 39 tokens

research_codebase

Document codebase as-is with thoughts directory for historical context.

hoblin/claude-ruby-marketplace · 11 tokens

iterate_plan

Iterate on existing implementation plans with thorough research and updates.

hoblin/claude-ruby-marketplace · 11 tokens