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 skills add chrisallenlane/claude-swe-workflows --skill refactorgit clone --depth 1 https://github.com/chrisallenlane/claude-swe-workflowsWrote 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/skills/chrisallenlane/claude-swe-workflows/refactor)<a href="https://agentmods.dev/skills/chrisallenlane/claude-swe-workflows/refactor"><img src="https://agentmods.dev/badge/skills/chrisallenlane/claude-swe-workflows/refactor.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.00047 | $0.03275 |
| Opus 5 | $0.00023 | $0.01638 |
| Sonnet 5 | $0.00009 | $0.00655 |
| Haiku 4.5 | $0.00005 | $0.00328 |
Grade A, and why
refactor 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 8d 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor - Iterative Code Quality Improvement
Autonomous refactoring workflow that iteratively improves code quality within the existing architecture, always preferring the least aggressive change available, until no further opportunities exist.
Philosophy
Clarity is the goal. Every iteration should make the codebase easier to form a correct mental model of. Red diffs are the strongest signal - less code almost always means clearer code, and every iteration should delete more than it adds. But when reducing lines would hurt comprehensibility, clarity wins.
Err on the side of trying. When uncertain whether a refactoring is worthwhile, attempt it anyway. Git makes failed experiments free - the workflow will revert changes that don't pass QA. Missed opportunities are invisible; failed attempts teach you something. Be bold, knowing that version control provides the safety net.
Work within the existing architecture. This workflow improves code quality - DRY, dead code, naming, complexity - without questioning module boundaries or reorganizing the system. For architectural analysis (noun extraction, module dissolution, blueprint-driven restructuring), use /review-arch instead.
Workflow Overview
┌─────────────────────────────────────────────────────┐
│ REFACTORING LOOP │
├─────────────────────────────────────────────────────┤
│ 1. Determine scope │
│ 2. Select aggression ceiling │
│ 3. Gather QA instructions │
│ 4. Spawn fresh swe-code-reviewer agent (full scan) │
│ 5. Select least aggressive changes available │
│ 6. If none remain → exit to summary │
│ 7. Spawn SME agent (implement batch) │
│ 8. Spawn QA agent (verify) │
│ ├─ PASS → commit, goto 4 │
│ └─ FAIL → retry (max 3), then abort batch │
│ 9. Completion summary │
│ 10. Update documentation (/tidy-docs) │
└─────────────────────────────────────────────────────┘
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 387 lines · 47 tokens per session scan A af882f84d245
refactor is a skill published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 3,275 once invoked, about $0.0002 per session on Opus 5. 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-30.
Other skills, from other repositories
afc:release-notes
Generate release notes from git history.
afc:clean
Pipeline artifact cleanup and codebase hygiene.
afc:issue
Analyze GitHub issue — investigate bug reports, understand requirements, inspect issues.
afc:launch
Generate release artifacts — version bump, changelog, release tags.
afc:learner
Review and promote learned patterns to project rules.
afc:qa
Project quality audit — test confidence, error handling gaps, code health.