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/evan043/claude-cli-advanced-starter-pack/refactor-prep.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/refactor-prep.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/refactor-prep.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/refactor-prep.template.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.01147 |
| Opus 5 | $0.00000 | $0.00574 |
| Sonnet 5 | $0.00000 | $0.00229 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade C, and why
refactor-prep.template scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules/.cache dist/ How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Pre-refactoring safety checklist - ensure safe refactoring conditions
Refactor Prep
Comprehensive safety checklist before starting any refactoring work. Ensures you can safely make changes and recover if needed.
Usage
/refactor-prep
/refactor-prep --scope src/components
/refactor-prep --quick # Abbreviated checklist
Safety Checklist
1. Git Status
- Working directory is clean
- On correct branch (not main/master)
- Remote is up to date
2. Test Coverage
- All tests passing
- Affected code has test coverage
- E2E tests available for critical paths
3. Backup Points
- Create rollback commit/tag
- Document current behavior
- Screenshot/record current UI state
4. Dependencies
- No pending dependency updates
- Lock file is committed
- Build succeeds
5. Documentation
- Refactoring scope defined
- Breaking changes identified
- Migration plan documented
Implementation
Step 1: Git Safety Check
# Check working directory
git status
# Verify branch
git branch --show-current
# Check sync with remote
git fetch && git status -uno
Step 2: Test Status
# Run full test suite
npm test
# Check coverage for affected files
npm run coverage -- --collectCoverageFrom="src/components/**"
Step 3: Create Rollback Point
# Tag current state
git tag pre-refactor-$(date +%Y%m%d)
# Create backup branch
git branch backup/pre-refactor-$(date +%Y%m%d)
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 · 203 lines · 0 tokens per session scan C c2e20edd84e8
refactor-prep.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,147 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.