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 skills/timothywarner/copilot-dev/legacy-code-refactornpx skills add timothywarner/copilot-dev --skill legacy-code-refactorgit clone --depth 1 https://github.com/timothywarner/copilot-devWhat 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.00085 | $0.02387 |
| Opus 5 | $0.00043 | $0.01193 |
| Sonnet 5 | $0.00017 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00239 |
Grade A, and why
legacy-code-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 2d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legacy Code Refactor Skill
You are an expert in safely modernizing legacy JavaScript/TypeScript codebases. When this skill activates, follow the five-step methodology below precisely. Never change observable behavior — only improve the structure, readability, and maintainability.
The Core Principle
"Refactoring is changing the internal structure of software without changing its observable behavior." — Martin Fowler
Every transformation must be provably safe: the code must do the same thing before and after.
Step 1: Audit — Identify All Anti-Patterns
Read the target file completely, then produce an audit table listing every issue found:
| # | Line | Anti-Pattern | Why It's a Problem | Safe Fix |
|---|---|---|---|---|
| 1 | 3 | var in function scope |
var is function-scoped and hoisted; causes subtle bugs |
Replace with const or let |
| 2 | 12 | Nested callback (callback hell) | Impossible to reason about error flow; unreadable | Rewrite with async/await |
| 3 | 25 | prototype method |
No encapsulation; harder to subclass; verbose | Convert to class with methods |
| 4 | 31 | Magic number 86400000 |
Intent is invisible; breaking change if the value changes | Extract to named constant MS_PER_DAY |
| 5 | 44 | No error handling | Unhandled rejections crash Node.js silently | Wrap in try/catch |
| 6 | 55 | Mixed concerns | Validation + persistence + response in one function | Separate into distinct functions |
Present this table to the user before making any changes.
Step 2: Catalog of Anti-Patterns and Safe Fixes
2.1 var → const / let
// BEFORE — var is function-scoped and hoisted; assignment in loops leaks
var maxRetries = 3;
var i;
for (var i = 0; i < maxRetries; i++) { ... }
// AFTER — const for values that don't change, let for loop variables
const MAX_RETRIES = 3;
for (let i = 0; i < MAX_RETRIES; i++) { ... }
Safe when: The variable is not re-declared in the same scope (var allows re-declaration; let/const do not).
What ships with it
2 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.
- 2d ago First seen · 275 lines · 85 tokens per session scan A 55fc9357475d
legacy-code-refactor is a skill published in the GitHub repository timothywarner/copilot-dev (46 stars, last pushed 29d ago), licensed MIT. It adds 85 tokens to every session and 2,387 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…