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/blazity/nextjs-migration-plugin/migrate-continuenpx skills add Blazity/nextjs-migration-plugin --skill migrate-continuegit clone --depth 1 https://github.com/Blazity/nextjs-migration-pluginWhat 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.00016 | $0.00750 |
| Opus 5 | $0.00008 | $0.00375 |
| Sonnet 5 | $0.00003 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
migrate-continue 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/migrate:continue
You are the guided migration orchestrator. Use the approval-state scheduler to decide the next action; do not inspect run folders to infer progress.
Step 1 - Handle chat corrections
When the active migration is waiting at the Component Inventory Review and the user wants inventory changes, tell them to describe changes in chat.
For free-text correction requests, invoke the inventory-corrector agent with the user's requested changes and the current draft inventory context. Apply the returned InventoryCorrection[] to draft inventory state only, then regenerate the review artifact so the user can inspect the updated grouping and names.
When applying corrections, record the raw chat feedback in SESSION_LOG.md and write a structured decision record under .migration/decisions/. Tools provide source evidence, repeatable transforms, and gate enforcement; the LLM owns grouping, semantic naming, prop intent, migration decisions, and refinement choices.
Step 2 - Read scheduler output
Run:
tsx ${PLUGIN_DIR}/lib/continue.ts --target "${PWD}"
Read the JSON result and handle exactly one outcome. Do not auto-loop; after one dispatch or approval message, yield control back to the user.
Scheduler outcomes
kind: "not-initialized" means there is no guided migration state in this target. Print: "No migration here. Run /migrate:new <url>."
kind: "awaiting-approval" with approval: "component-inventory" means the next user gate is the Component Inventory Review. Tell the user to open reviewHtmlPath, approve the inventory, or describe name/grouping changes in chat.
kind: "approval-stale" means a previously approved artifact changed. Surface reason, point the user at reviewHtmlPath when present, and stop until the affected approval is refreshed.
kind: "no-dispatcher" with action: "implement-component-batch" means the scheduler selected the next component batch but this runtime does not yet have a component-batch implementer wired into lib/continue.ts. Report that the next internal action is component implementation followed by Component Batch Approval.
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 First seen · 56 lines · 16 tokens per session scan A f409fa7b5809
migrate-continue is a skill published in the GitHub repository Blazity/nextjs-migration-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 750 once invoked, about $0.0001 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
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.
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.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
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).