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 d-o-hub/github-template-ai-agents --skill migration-refactoringgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/d-o-hub/github-template-ai-agents/migration-refactoring)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/migration-refactoring"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/migration-refactoring/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/skills/d-o-hub/github-template-ai-agents/migration-refactoring"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/migration-refactoring.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.00136 | $0.02093 |
| Opus 5.5 | $0.00054 | $0.00837 |
| Sonnet 5.5 | $0.00027 | $0.00419 |
| Haiku 4.5 | $0.00014 | $0.00209 |
Grade A, and why
migration-refactoring 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 yesterday.
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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration & Refactoring
Systematic approach to complex code migrations, structural refactorings, and move-only decompositions with safety guardrails and rollback capabilities.
When to Use
- Move-only decomposition - Splitting large files near size ceilings (e.g., 500 LOC limits) without behavioral change ("split this large file", "extract module", "keep diff move-only")
- Dependency upgrades that force source changes - Major bumps with breaking APIs; routine patch/minor/CVE bumps go to
dependency-upgrades - Framework migrations - React class→hooks, Flask→FastAPI, Django→DRF, etc.
- Language modernizations - Python 2→3, JavaScript→TypeScript
- Large-scale refactoring - Cross-file changes requiring structural consistency
- Database schema evolution - Migrations with data transformation
- Monorepo decomposition - Extracting services from monoliths
When NOT to Use
- Routine patch/minor/CVE dependency upgrades - Use
dependency-upgrades - Static analysis and linter-only fixes - Use
static-analysis - PR code reviews and feedback analysis - Use
code-review-assistant
Move-Only Decomposition Workflow
Dedicated procedure for splitting large files without behavioral change. Keep distinct from semantic migrations with intentional logic or interface changes.
- Establish Trigger & Baseline: Document the LOC/complexity ceiling warning (e.g., 500 LOC). Verify test suite passes before edits.
- Identify Extraction Seams: Analyze cohesive module boundaries. Map public/private visibility, imported dependencies, initialization sequence, and test ownership. Watch for circular deps or global state.
- Mechanical Move: Extract code purely mechanically. Do not mix behavioral refactoring, performance tweaks, or reformatting into the move commit.
- Validate Tests: Run narrow unit tests first, followed by full repository quality gate checks (
scripts/quality_gate.sh). - Review Move-Aware Diff: Inspect diff using
git diff --find-renames(git diff -M) to verify pure structural relocation without line edits or type changes. - Handle Unintentional Semantic Changes: If behavior changes were added accidentally, stop, revert or isolate them into a separate commit/PR with dedicated tests.
- Revise Seam Boundaries: If tests fail or contracts break, re-evaluate seam boundaries and visibility before re-attempting the move.
What ships with it
7 files 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.
- yesterday Changed · +20 lines · +16 tokens per session 020d2f74adbd
- 25d ago Changed · +1 lines · +19 tokens per session ce692402f59f
- 1mo ago First seen · 217 lines · 101 tokens per session scan A 932ec79bec46
migration-refactoring is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It adds 136 tokens to every session and 2,093 once invoked, about $0.0005 per session on Opus 5.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
document-code
Decide whether a comment belongs, and write the ones that do — in Ruby, YAML, a Dockerfile, a shell script, tests or config. Use it before adding any comment, docstring or YARD block, including one you are about to write mid-implementation, and before deleting or rewording one already there. Use it when finished code…
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
create_plan
Create detailed implementation plans through interactive research and iteration.
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…