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 Blazity/nextjs-migration-plugin --skill migrate-helpgit clone --depth 1 https://github.com/Blazity/nextjs-migration-pluginWrote 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/blazity/nextjs-migration-plugin/migrate-help)<a href="https://agentmods.dev/skills/blazity/nextjs-migration-plugin/migrate-help"><img src="https://agentmods.dev/badge/skills/blazity/nextjs-migration-plugin/migrate-help/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/blazity/nextjs-migration-plugin/migrate-help"><img src="https://agentmods.dev/badge/skills/blazity/nextjs-migration-plugin/migrate-help.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.00020 | $0.00487 |
| Opus 5.5 | $0.00008 | $0.00195 |
| Sonnet 5.5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
migrate-help 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 1mo 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
migrate-help
You are explaining how to use the Next.js migration plugin. This command is read-only. Do not create .migration/, mutate config, run migration work, or invoke /migrate:continue.
Step 1 - Print Static Help
Print this help content in a concise, user-facing format:
Next.js Migration Plugin
Use the guided flow to migrate a public website into a Next.js App Router project with resumable state, component inventory review, component batch approval, and page layout approval.
Commands
- /migrate:new <url> starts a migration and opens Component Inventory Review.
- /migrate:continue resumes the next required approval or implementation step.
- /migrate:status prints current approval, component, page, and queue state.
- /migrate:help shows this help.
Recovery
lower-level scripts and library entry points still exist for maintainers, but they are advanced/recovery tools and are not part of the normal command flow.
Keep the help static even if a local migration exists. Only the final paragraph should depend on local state.
Step 2 - Context-aware final paragraph
Run the status script and use its JSON to append one final paragraph:
tsx ${PLUGIN_DIR}/lib/status.ts --target "${PWD}"
If ${PLUGIN_DIR} is not set by the harness, resolve it from the plugin install path.
If the script returns initialized: false, append:
No migration in this directory. Start with
/migrate:new <url>.
If the script returns initialized: true, count component and page approval statuses, then append:
Current context: migrating
[sourceUrl]; inventory[approvals.inventory]; components[approved] approved, [pending] pending, [stale] stale; pages[approved] approved, [stale] stale; browser queue concurrency[queueConcurrency]. Next, run/migrate:continueto resume the guided flow, or/migrate:statusfor the full approval summary.
If the status script fails because local state is invalid, append:
Local migration state could not be read:
[error message]. Run/migrate:statusfor the full diagnostic.
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.
- 1mo ago First seen · 53 lines · 20 tokens per session scan A 85dcc3d0f86b
migrate-help is a skill published in the GitHub repository Blazity/nextjs-migration-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 487 once invoked, about $0.0001 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
arcgis-to-portaljs
Migrate a whole ArcGIS Hub site into a PortalJS Arc portal end-to-end. Harvests the Hub /data.json (DCAT-US) inventory, exports every FeatureService layer through the ArcGIS REST query API with resultOffset paging, converts each to the serverless dual tier (PMTiles render + GeoParquet query) with tabular items to…
portaljs-migrate
Migrate (harvest) datasets between open-data platforms. Reads CKAN, a DCAT-US /data.json catalog (DKAN, ArcGIS Hub, data.gov), a DCAT / DCAT-AP RDF feed (JSON-LD, Turtle, or RDF/XML), Socrata, OpenDataSoft, or an ArcGIS FeatureServer, and writes them to a static PortalJS catalog or pushes them into a CKAN instance…
nextjs-upgrade
Next.js version migrations using official guides and codemods. Use when migrating a Next.js project to a new major version using codemods.
next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods.
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).