Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mickeyyaya/refactoring-skillsnpx agentmods add skills/mickeyyaya/refactoring-skills/refactorWrote 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/mickeyyaya/refactoring-skills/refactor)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/refactor"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/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.00044 | $0.03915 |
| Opus 5 | $0.00022 | $0.01958 |
| Sonnet 5 | $0.00009 | $0.00783 |
| Haiku 4.5 | $0.00004 | $0.00392 |
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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/refactor — Full Refactoring Pipeline
Overview
Single entry point that orchestrates the complete refactoring workflow: detect smells → prioritize → partition into independent groups → execute in parallel worktrees via subagents → merge & verify.
Auto Mode Detection
Before starting, check if the user is in bypass/yolo mode (auto-accept permissions enabled). Detection signals:
- User explicitly said "yolo mode", "bypass permissions", or "auto-accept"
- The session is running with
--dangerously-skip-permissionsor equivalent - Tools are being auto-approved without user prompts
When auto mode is detected: Skip all confirmation prompts. Automatically select all issues, partition, launch parallel subagents, and merge passing branches without pausing. This enables fully autonomous refactoring.
When auto mode is NOT detected: Pause for user confirmation at each checkpoint as described below.
Git Isolation (MANDATORY)
All refactoring work MUST be done in isolated git worktrees branched from main. Never commit directly to main.
Execution Modes
The orchestrator selects the execution mode based on the partition result from Phase 3:
| Condition | Mode | Worktrees |
|---|---|---|
| 1 group or all issues touch the same files | Sequential | 1 worktree, 1 branch |
| N independent groups with no file overlap | Parallel | N worktrees, N branches, N subagents |
Worktree Naming Convention
../refactor-wt-<group-slug> → branch: refactor/<group-slug>
Examples:
../refactor-wt-extract-auth → refactor/extract-auth
../refactor-wt-simplify-payment → refactor/simplify-payment
../refactor-wt-cleanup-utils → refactor/cleanup-utils
Workflow
Phase 1 SCAN ──────────── on main (read-only)
Phase 2 PRIORITIZE ────── on main (read-only)
Phase 3 PLAN & PARTITION ─ on main (read-only, dependency analysis)
Phase 4 EXECUTE ────────── in worktrees (parallel subagents)
Phase 5 MERGE & VERIFY ── back on main (sequential merge, final scan)
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 · 400 lines · 44 tokens per session scan A 781bd195aa6b
refactor is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 3,915 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-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…