What is refactor-clean?

A code-cleanup command that finds unused code and repeated implementations, then removes or combines them after checking their use.

Use it to find unused imports, functions, exports, files, dependencies, and CSS classes, and to consolidate copy-pasted or similar code.

It reduces clutter and duplication that make a codebase harder to understand and maintain. Checks and tests help avoid removing code that is still needed.

refactor-clean — Command by tpavanipradeep

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/tpavanipradeep/everything-claude-code/refactor-clean

Clone the repo

git clone --depth 1 https://github.com/tpavanipradeep/everything-claude-code

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 505 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00006	$0.00505
Opus 5	$0.00003	$0.00253
Sonnet 5	$0.00001	$0.00101
Haiku 4.5	$0.00001	$0.00051

Measured 2d ago against content hash 4f2dec090219, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

refactor-clean 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 2d 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.

Origin

This is a copy

100% identical to refactor-clean — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.opencode/commands/refactor-clean.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Refactor Clean Command

Analyze and clean up the codebase: $ARGUMENTS

Your Task

Detect dead code using analysis tools
Identify duplicates and consolidation opportunities
Safely remove unused code with documentation
Verify no functionality broken

Detection Phase

Run Analysis Tools

# Find unused exports
npx knip

# Find unused dependencies
npx depcheck

# Find unused TypeScript exports
npx ts-prune

Manual Checks

Unused functions (no callers)
Unused variables
Unused imports
Commented-out code
Unreachable code
Unused CSS classes

Removal Phase

Before Removing

Search for usage - grep, find references
Check exports - might be used externally
Verify tests - no test depends on it
Document removal - git commit message

Safe Removal Order

Remove unused imports first
Remove unused private functions
Remove unused exported functions
Remove unused types/interfaces
Remove unused files

Consolidation Phase

Identify Duplicates

Similar functions with minor differences
Copy-pasted code blocks
Repeated patterns

Consolidation Strategies

Extract utility function - for repeated logic
Create base class - for similar classes
Use higher-order functions - for repeated patterns
Create shared constants - for magic values

Verification

After cleanup:

npm run build - builds successfully
npm test - all tests pass
npm run lint - no new lint errors
Manual smoke test - features work

Report Format

Dead Code Analysis
==================

Removed:
- file.ts: functionName (unused export)
- utils.ts: helperFunction (no callers)

Consolidated:
- formatDate() and formatDateTime() → dateUtils.format()

Remaining (manual review needed):
- oldComponent.tsx: potentially unused, verify with team

CAUTION: Always verify before removing. When in doubt, ask or add // TODO: verify usage comment.

Read the full file on GitHub · 103 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.

2d ago First seen · 103 lines · 6 tokens per session scan A 4f2dec090219

Subscribe to this mod's changes

refactor-clean is a command published in the GitHub repository tpavanipradeep/everything-claude-code (104 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 505 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to refactor-clean, differing in 0 lines, and is treated as a copy.

Frontend Writing and docs

refactor-clean