refactor-clean

A cautious process for finding and removing unused code, with tests run before and after changes.

In plain words
What is it for?
It is for analysing unused code, recording findings, removing safe items, and verifying the project with focused and full tests.
Why use it?
It helps reduce dead code while lowering the risk of deleting something that is still needed.

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/cloudnative-co/claude-code-starter-kit/refactor-clean
Clone the repo
git clone --depth 1 https://github.com/cloudnative-co/claude-code-starter-kit
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 246 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.00246
Opus 5 $0.00000 $0.00123
Sonnet 5 $0.00000 $0.00049
Haiku 4.5 $0.00000 $0.00025

Measured 2d ago against content hash 7dabebbd1b6a, 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 · 28 lines

What it actually says

Refactor Clean

Safely identify and remove dead code with test verification:

  1. Run dead-code analysis appropriate to the project language (e.g. knip/depcheck/ts-prune for JS/TS, vulture for Python, deadcode for Go, shellcheck + reference grep for shell).

  2. Generate a report (e.g. .reports/dead-code-analysis.md).

  3. Categorize findings by severity:

    • SAFE: Test files, unused internal utilities
    • CAUTION: Public APIs / exported interfaces, route handlers, UI components
    • DANGER: Config files, main entry points
  4. Verification flow:

    • Run the full test suite once to establish a green baseline
    • Apply SAFE deletions as a batch, one commit per deletion or logical group (easy rollback)
    • Run focused tests per batch, then the full suite once at the end
    • On failure, bisect the batch and revert only the offending deletion
    • Handle CAUTION items individually with focused tests
    • DANGER items are report-only — do not delete
  5. Show summary of cleaned items

Never delete code without running tests first!

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 · 28 lines · 0 tokens per session scan A 7dabebbd1b6a

Subscribe to this mod's changes

refactor-clean is a command published in the GitHub repository cloudnative-co/claude-code-starter-kit (147 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 246 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.