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 hubvue/skills --skill project-migrationgit clone --depth 1 https://github.com/hubvue/skillsWrote 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/hubvue/skills/project-migration)<a href="https://agentmods.dev/skills/hubvue/skills/project-migration"><img src="https://agentmods.dev/badge/skills/hubvue/skills/project-migration.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.00137 | $0.01025 |
| Opus 5 | $0.00068 | $0.00513 |
| Sonnet 5 | $0.00027 | $0.00205 |
| Haiku 4.5 | $0.00014 | $0.00103 |
Grade A, and why
project-migration 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 7d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Migration
Treat the request as project migration, repository migration, or engineering-system migration by default. Optimize for business continuity, behavior parity, rollback safety, and controlled scope rather than opportunistic rewrites.
Do not use this skill when the user mainly wants a project handover or successor-facing takeover document without a real migration goal. In those cases, prefer project-handover-generator.
Workflow
Use this default phase order unless the user explicitly narrows the request:
intake -> audit -> map -> diff -> plan -> pilot -> execute -> verify -> cleanup
If the user does not specify a phase, complete only the current phase, then stop and present outputs, status, risks, and the recommended next phase.
If the user specifies a phase, complete the minimum prerequisite phases needed to produce a credible result. If phase artifacts already exist, update them instead of restarting.
If the user changes an earlier phase after later-phase work already exists, revise the earlier phase first and then check all affected downstream phases.
Operating Rules
- Prefer migration-first, governance-later unless the user explicitly wants a broader rewrite.
- Audit inherited or undocumented projects before giving large migration execution advice.
- Split work by business slice, route slice, or flow by default. Use file, package, or module units only when dependency structure is the real migration boundary.
- Prefer adapters, bridge layers, or compatibility layers for major old-vs-new differences before rewriting business logic.
- Inspect and record hidden dependencies, especially globally registered components, global mixins, prototype injections, env vars, route guards, permission injection, analytics, monitoring, theme variables, upload and download behavior, bootstrap logic, global styles, and
windowinjections. - State assumptions and unknowns explicitly when information is incomplete.
- Produce concrete artifacts, preferably under
docs/migration/, rather than only conversational advice. - Report every phase with the current phase, inputs, actions, outputs, exit criteria, risks, and next step.
- Select and record a migration posture: structure-preserving, redesign, incremental, or hybrid.
- Establish a credible objective Judge before broad execution. Validate it against the old baseline, repeatability, and a safe isolated negative control.
- Use a durable queue or manifest as the source of truth. Do not infer completion from chat history or file existence alone.
- Separate implementation and independent review responsibilities. Multi-agent execution is optional; use a fresh restricted-context review pass when working with one agent.
- When failures repeat across units, fix the Rulebook, Judge, queue, or workflow that produced them, then revalidate the affected scope.
What ships with it
8 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.
- 7d ago First seen · 71 lines · 137 tokens per session scan A c6ea330b78d4
project-migration is a skill published in the GitHub repository hubvue/skills (6 stars, last pushed 6d ago), licensed MIT. It adds 137 tokens to every session and 1,025 once invoked, about $0.0007 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.