refactor-code

refactor-code is a command for Claude Code from muyen/vibe-to-prod. It costs 7 tokens per session (331 once invoked), scanned A, original, MIT.

A refactoring command guides code changes that improve structure without changing intended behaviour, while checking test results before and after. Refactoring means restructuring existing code without changing what it does.

In plain words
What is it for?
It is for extracting functions, renaming or moving code, simplifying logic, removing dead code, and verifying tests and performance afterward.
Why use it?
It helps reduce the risk of breaking working software while making code easier to maintain.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit It is for extracting functions, renaming or moving code, simplifying logic, removing dead code, and verifying tests and performance afterward.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/muyen/vibe-to-prod/refactor-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.

Clone the repo
git clone --depth 1 https://github.com/muyen/vibe-to-prod

Made for: Claude Code.

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

agentmods badge for refactor-code

README.md
[![agentmods](https://agentmods.dev/badge/commands/muyen/vibe-to-prod/refactor-code/github.svg)](https://agentmods.dev/commands/muyen/vibe-to-prod/refactor-code)
Your own site
<a href="https://agentmods.dev/commands/muyen/vibe-to-prod/refactor-code"><img src="https://agentmods.dev/badge/commands/muyen/vibe-to-prod/refactor-code/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.

agentmods 80×15 button for refactor-code

Your own site · 80×15
<a href="https://agentmods.dev/commands/muyen/vibe-to-prod/refactor-code"><img src="https://agentmods.dev/badge/commands/muyen/vibe-to-prod/refactor-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00007 $0.00331
Opus 5.5 $0.00003 $0.00132
Sonnet 5.5 $0.00001 $0.00066
Haiku 4.5 $0.00001 $0.00033

Measured 12d ago against content hash 0f14c17ae352, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

refactor-code 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 12d 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.

.claude/commands/refactor-code.md · 67 lines

What it actually says

Refactor Code

Refactor: $ARGUMENTS

Pre-Refactoring Checklist

  • Tests exist for code being refactored
  • Current tests pass
  • Understand ALL usages of code

Process

  1. Verify Test Coverage

    # Backend
    cd backend && go test ./... -v
    
    # iOS - Build and run tests
    cd mobile/ios && make test
    
    # Android
    cd mobile/android && ./gradlew test
    
  2. Refactoring Techniques

    • Extract Method/Function
    • Rename Variable/Method
    • Move Method/Field
    • Eliminate Dead Code
    • Simplify Conditionals
  3. Incremental Changes

    • Small, focused changes
    • Run tests after EACH change
    • Commit working changes frequently
  4. Verify After Refactoring

    • All tests still pass
    • No new linter warnings
    • Performance not degraded

Patterns to Follow

Backend (Go):

  • Keep handlers thin (delegate to services)
  • Services contain business logic
  • Repositories handle data access

Mobile:

  • MVVM architecture
  • Repository pattern for data
  • Dependency injection via constructors

Output

Provide:

  1. Files modified
  2. Summary of changes
  3. Test results before/after
  4. Any risks or considerations
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. 12d ago First seen · 67 lines · 7 tokens per session scan A 0f14c17ae352

Subscribe to this mod's changes

refactor-code is a command published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 331 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-10-04.