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 lisbeth718/pseo-skills --skill seo-migrationgit clone --depth 1 https://github.com/lisbeth718/pseo-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/lisbeth718/pseo-skills/seo-migration)<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/seo-migration"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/seo-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/lisbeth718/pseo-skills/seo-migration"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/seo-migration.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.00074 | $0.02689 |
| Opus 5.5 | $0.00030 | $0.01076 |
| Sonnet 5.5 | $0.00015 | $0.00538 |
| Haiku 4.5 | $0.00007 | $0.00269 |
Grade A, and why
seo-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 6d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Migration
Move URLs without losing indexing, rankings or backlink value. Source: site moves with URL changes.
Core Principles
- Every old URL that had value maps 1:1 to its closest new equivalent with a server-side permanent redirect (301 or 308)
- One change at a time: do not combine a domain move, redesign, URL restructure and content rewrite, or you cannot diagnose drops
- No chains, no loops: old URL goes straight to the final URL
- No mass-redirect to the home page: irrelevant targets are treated as soft 404s and pass nothing
- Measure before and after: a baseline is the only way to know if the migration worked
- Reversible: keep the old site and a rollback path until metrics stabilize
Migration Types
| Type | Change of Address | Notes |
|---|---|---|
| URL structure / path change | No | Redirects + sitemap |
| Domain or subdomain move | Yes (old site) | Verify all variants, redirects site-wide |
| HTTP to HTTPS, www toggle | No | Redirect + canonicals + GSC property for new variant |
| Platform / framework change (URLs unchanged) | No | Verify rendering parity, keep URLs identical |
| Merge sites | Only if a whole domain goes away | Map each section to its closest page on the target |
| Add locale prefixes | No | See seo-i18n |
Phase 1: Pre-Migration Inventory
Build the full list of old URLs from several sources, since no single one is complete:
- Crawl the live site (Screaming Frog, or
Glob/data layer for pSEO: every route the generator can emit) - Sitemaps (all of them, including image/video)
- GSC: Performance export (all pages with impressions, last 16 months), Pages report (indexed list), Links report (top linked pages)
- Analytics: landing pages with sessions/conversions
- Backlinks: Ahrefs/Semrush/GSC export of linked URLs
- Server logs: URLs Googlebot actually requests, plus non-HTML assets (images, PDFs, JS, CSS)
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.
- 6d ago First seen · 191 lines · 74 tokens per session scan A 27f1c2cc3e3d
seo-migration is a skill published in the GitHub repository lisbeth718/pseo-skills (54 stars, last pushed 6d ago), licensed MIT. It adds 74 tokens to every session and 2,689 once invoked, about $0.0003 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-10-12.
Other skills, from other repositories
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.