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/sangrokjung/claude-forge/refactor-cleangit clone --depth 1 https://github.com/sangrokjung/claude-forgeWrote 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/sangrokjung/claude-forge/refactor-clean)<a href="https://agentmods.dev/commands/sangrokjung/claude-forge/refactor-clean"><img src="https://agentmods.dev/badge/commands/sangrokjung/claude-forge/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.1 | $0.00010 | $0.00288 |
| Opus 5 | $0.00005 | $0.00144 |
| Sonnet 5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
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 6d 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.
This is a copy
86% identical to refactor-clean — 31 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.
What it actually says
Refactor Clean
참고: 대규모 리팩토링(3파일 이상 변경 예상)은
/plan을 먼저 실행하세요 (Golden Principle #9: HARD-GATE).
Safely identify and remove dead code with test verification:
-
Run dead code analysis tools:
- knip: Find unused exports and files
- depcheck: Find unused dependencies
- ts-prune: Find unused TypeScript exports
-
Generate comprehensive report in .reports/dead-code-analysis.md
-
Categorize findings by severity:
- SAFE: Test files, unused utilities
- CAUTION: API routes, components
- DANGER: Config files, main entry points
-
Propose safe deletions only
-
Before each deletion:
- Run full test suite
- Verify tests pass
- Apply change
- Re-run tests
- Rollback if tests fail
-
Show summary of cleaned items
Never delete code without running tests first!
다음 단계
| 리팩토링이 끝나면 | 커맨드 |
|---|---|
| 코드 검사 | /code-review |
| 빌드/테스트 검증 | /handoff-verify |
| 문서 동기화 | /sync |
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.
- 6d ago First seen · 45 lines · 10 tokens per session scan A 4d18a5939f76
refactor-clean is a command published in the GitHub repository sangrokjung/claude-forge (825 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 288 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to refactor-clean, differing in 31 lines, and is treated as a copy.
Other commands, from other repositories
CONTEXT
Slash commands for SPEC-First development workflow.
review
Review plans with multi-angle analysis (mandatory + extended + autonomous).
review
Perform a thorough code review of changes in this branch.
01_confirm
Extract plan from conversation, create file in draft/, auto-apply non-BLOCKING improvements, move to pending.
add-tool
Scaffold and implement a new tool for VisionAgent.
implement
You are in full autonomous implementation mode. Follow the VisionAgent agentic task approach from CLAUDE.md rigorously.