refactor-clean

A cleanup command that finds unused code and dependencies, writes a report, and recommends removals classified by risk. It requires tests before and after each deletion.

In plain words
What is it for?
Use it to inspect unused exports, files, dependencies, and TypeScript code, then safely remove only items supported by passing tests.
Why use it?
It reduces the risk of deleting code that is still needed by requiring analysis, testing, and rollback when tests fail.

Command

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/codelably/harmony-claude-code/refactor-clean
Clone the repo
git clone --depth 1 https://github.com/codelably/harmony-claude-code
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 237 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.00000 $0.00237
Opus 5 $0.00000 $0.00118
Sonnet 5 $0.00000 $0.00047
Haiku 4.5 $0.00000 $0.00024

Measured 2d ago against content hash 98827b4d00a8, 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.

commands/refactor-clean.md · 29 lines

What it actually says

重构清理 (Refactor Clean)

安全地识别并通过测试验证移除死代码(Dead Code):

  1. 运行死代码分析工具:

    • knip:查找未使用的导出和文件
    • depcheck:查找未使用的依赖
    • ts-prune:查找未使用的 TypeScript 导出
  2. .reports/dead-code-analysis.md 中生成详细报告

  3. 按严重程度对结果进行分类:

    • 安全(SAFE):测试文件、未使用的工具类
    • 谨慎(CAUTION):API 路由、组件
    • 危险(DANGER):配置文件、主入口点
  4. 仅建议进行安全的删除

  5. 在每次删除之前:

    • 运行完整的测试套件
    • 验证测试通过
    • 应用更改
    • 重新运行测试
    • 如果测试失败则回滚
  6. 显示已清理项的摘要

严禁在未运行测试的情况下删除代码!

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. 2d ago First seen · 29 lines · 0 tokens per session scan A 98827b4d00a8

Subscribe to this mod's changes

refactor-clean is a command published in the GitHub repository codelably/harmony-claude-code (42 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 237 tokens. 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-30.