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.
git 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-workflow.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/refactor-workflow.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/refactor-workflow.template/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/refactor-workflow.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/refactor-workflow.template.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02667 |
| Opus 5.5 | $0.00000 | $0.01067 |
| Sonnet 5.5 | $0.00000 | $0.00533 |
| Haiku 4.5 | $0.00000 | $0.00267 |
Grade B, and why
refactor-workflow.template scanned grade B 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 2mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/refactor-audit.json How it starts
The opening of the file, as written. The whole thing — 370 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: Guided refactoring workflow with branch, task list, and GitHub issue model: sonnet argument-hint: [file path or 'flagged']
/refactor-workflow - Guided Refactoring Workflow
Start a comprehensive refactoring workflow with branch management, task list creation, GitHub issue tracking, and specialist agent deployment.
Quick Start
/refactor-workflow # Refactor all flagged files
/refactor-workflow src/api/client.ts # Refactor specific file
/refactor-workflow --list # View all flagged files
/refactor-workflow --dismiss # Dismiss current suggestions
Workflow Overview
╔═══════════════════════════════════════════════════════════════╗
║ 🔄 Refactor Workflow ║
╠═══════════════════════════════════════════════════════════════╣
║ ║
║ Step 1: Analyze file(s) for refactoring opportunities ║
║ Step 2: Create feature branch (refactor/filename-cleanup) ║
║ Step 3: Generate task list with specific refactor tasks ║
║ Step 4: Create GitHub issue to track progress ║
║ Step 5: Deploy specialist agent for tech stack ║
║ Step 6: Execute refactoring with commits per logical unit ║
║ Step 7: Run tests to verify no regressions ║
║ Step 8: Create PR for review ║
║ ║
╚═══════════════════════════════════════════════════════════════╝
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.
- 2mo ago First seen · 370 lines · 0 tokens per session scan B 6c6a85911cd6
refactor-workflow.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,667 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
refactor-workflow.template compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| refactor-workflow.templateevan043/claude-cli-advanced-starter-pack | Command | 61 | 3mo ago | MIT | B | 0 | Claude Code |
| watch-cidamusix/atomic-claude | Command | 116 | 5d ago | MIT | A | 69 | Claude Code |
| deploytravisjneuman/.claude | Command | 107 | yesterday | MIT | A | 8 | Claude Code |
| autosangrokjung/claude-forge | Command | 874 | 2mo ago | MIT | A | 20 | Claude Code |
| syncsangrokjung/claude-forge | Command | 874 | 2mo ago | MIT | A | 22 | Claude Code |
| auto-claudetravisjneuman/.claude | Command | 107 | yesterday | MIT | A | 10 | Claude Code |
| session-reportdamusix/atomic-claude | Command | 116 | 5d ago | MIT | A | 31 | Claude Code |