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.
npx agentmods add commands/rosudrag/ai-praxis/refactor-cleangit clone --depth 1 https://github.com/rosudrag/ai-praxisWrote 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.
[](https://agentmods.dev/commands/rosudrag/ai-praxis/refactor-clean)<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>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.00000 | $0.00685 |
| Opus 5 | $0.00000 | $0.00342 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00068 |
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.
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:
- Remove the dead code
- Run {{test_command}}
- If tests fail, revert immediately and recategorize as CAUTION
- Record what was removed and lines saved
Step 4: Review CAUTION Items
For each CAUTION item:
- Search the entire codebase for dynamic references (string literals, reflection, config)
- Check build scripts, CI configs, and documentation
- If confirmed dead, remove and run {{test_command}}
- 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:
- Search for near-duplicate functions (same logic, different names)
- Propose consolidation — do NOT auto-merge without confirmation
- If approved, consolidate one at a time, testing after each
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.
- 4d ago First seen · 98 lines · 0 tokens per session scan A 3eff0b99cb53
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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.