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 textura-agency/next16-claude-starter --skill site-migrationgit clone --depth 1 https://github.com/textura-agency/next16-claude-starterWrote 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/textura-agency/next16-claude-starter/site-migration)<a href="https://agentmods.dev/skills/textura-agency/next16-claude-starter/site-migration"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/site-migration/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/textura-agency/next16-claude-starter/site-migration"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/site-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.00948 |
| Opus 5 | $0.00041 | $0.00474 |
| Sonnet 5 | $0.00016 | $0.00190 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
site-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 12d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site migration without losing rankings
Traffic collapse after a relaunch is almost always the same cause: URLs changed and nothing told search engines where they went. The work below happens before the new site goes live. After launch it is damage control.
If the user is rebuilding a live site, raise this at the start of the project, not at the end. It is the cheapest insurance in the whole engagement.
1. Inventory the live site — before anything changes
Crawl or list every indexed URL. Record: URL, page title, H1, content type,
whether it currently ranks. Save to MIGRATION-URL-INVENTORY.md.
Sources, in order of reliability: the existing sitemap.xml, Search Console's Pages report, an actual crawl, the CMS's own page list. Use several — each misses different things, and the ones they miss (old landing pages, PDFs, paginated archives) are exactly the ones that quietly carry links.
2. Snapshot what you are protecting
Ask the user for a Google Search Console performance export (last 3–6 months: Performance → Export). From it record:
- top 20 pages by clicks
- top 30 queries by clicks and impressions
- everything ranking in positions 1–10
Save to MIGRATION-RANKINGS-SNAPSHOT.md. This is the baseline you will be judged
against, so capture it before the rebuild touches anything.
Also capture the most-linked pages (Ahrefs/Semrush export if they have one). A page with backlinks must keep its equity — losing it is far more expensive than losing an unlinked page.
3. Build the redirect map
MIGRATION-REDIRECT-MAP.md, two columns: old URL → new URL. Rules:
- Every old URL gets a destination. Mark unknowns
[TBD]and resolve them all before launch — a[TBD]at launch is a 404. - Map to the closest equivalent page, never blanket-redirect everything to the homepage. Google treats mass homepage redirects as soft 404s and the equity is lost.
- 301 (permanent), not 302, unless the change genuinely is temporary.
- One hop. Chained redirects leak and slow crawling — if the old site already redirects, map to the final destination.
- Preserve query-parameter and trailing-slash behaviour, or normalise it deliberately and consistently.
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.
- 12d ago First seen · 82 lines · 81 tokens per session scan A d8b8b64523bf
site-migration is a skill published in the GitHub repository textura-agency/next16-claude-starter (117 stars, last pushed 4d ago), licensed Unlicense. It adds 81 tokens to every session and 948 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…