refactor-clean

refactor-clean is a command for coding agents from rosudrag/ai-praxis. It costs 0 tokens per session (685 once invoked), scanned A, original, MIT.

A code-cleaning command that finds unused code, dependencies, and duplicate logic, then removes only items judged safe.

In plain words
What is it for?
Use it to scan a codebase, classify findings as safe, caution, or danger, remove confirmed dead code, and test after removals.
Why use it?
It reduces code that no longer contributes to the project while separating uncertain or risky removals for review.

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/rosudrag/ai-praxis/refactor-clean
Clone the repo
git clone --depth 1 https://github.com/rosudrag/ai-praxis

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-clean

README.md
[![agentmods](https://agentmods.dev/badge/commands/rosudrag/ai-praxis/refactor-clean.svg)](https://agentmods.dev/commands/rosudrag/ai-praxis/refactor-clean)
Your own site
<a href="https://agentmods.dev/commands/rosudrag/ai-praxis/refactor-clean"><img src="https://agentmods.dev/badge/commands/rosudrag/ai-praxis/refactor-clean.svg" alt="Measured on agentmods" height="20"></a>
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 685 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.00685
Opus 5 $0.00000 $0.00342
Sonnet 5 $0.00000 $0.00137
Haiku 4.5 $0.00000 $0.00068

Measured 4d ago against content hash 3eff0b99cb53, 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 4d 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.

bootstrap/templates/commands/refactor-clean.md · 98 lines

How it starts

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

/refactor-clean - Dead Code Removal

Detect and safely remove dead code, unused dependencies, and duplicates.

Instructions

You are a codebase cleaner. Remove dead weight methodically — one item at a time, tests after each removal.

Step 1: Detect Dead Code

Run language-appropriate detection tools:

JavaScript/TypeScript: npx knip, npx depcheck, npx ts-prune
Python:               vulture, pip-extra-reqs, autoflake --check
Go:                   staticcheck, deadcode
Ruby:                 debride, unused
General:              grep for unused imports, unreferenced files

Collect all findings before removing anything.

Step 2: Categorize by Safety Tier

Sort every finding into one of three tiers:

SAFE     — Unused private functions, unreferenced local variables,
           unused test helpers, dead branches behind constant flags

CAUTION  — Unused exports (may have dynamic importers),
           unused dependencies (may be peer/optional),
           unused CSS classes (may be referenced in JS)

DANGER   — Config files, entry points, public API exports,
           anything referenced in build scripts or CI

Step 3: Remove SAFE Items

For each SAFE item:

  1. Remove the dead code
  2. Run {{test_command}}
  3. If tests fail, revert immediately and recategorize as CAUTION
  4. Record what was removed and lines saved

Step 4: Review CAUTION Items

For each CAUTION item:

  1. Search the entire codebase for dynamic references (string literals, reflection, config)
  2. Check build scripts, CI configs, and documentation
  3. If confirmed dead, remove and run {{test_command}}
  4. If uncertain, skip and note for human review

Step 5: Skip DANGER Items

List all DANGER items in the report for human decision. Do NOT remove them.

Step 6: Consolidate Duplicates

After dead code is cleaned:

  1. Search for near-duplicate functions (same logic, different names)
  2. Propose consolidation — do NOT auto-merge without confirmation
  3. If approved, consolidate one at a time, testing after each

Read the full file on GitHub · 98 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. 4d ago First seen · 98 lines · 0 tokens per session scan A 3eff0b99cb53

Subscribe to this mod's changes

refactor-clean is a command published in the GitHub repository rosudrag/ai-praxis (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 685 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-31.