migration-planner

migration-planner is a skill for Codex from sergekostenchuk/ui-ux-agent-skill-system. It costs 61 tokens per session (575 once invoked), scanned A, original, Apache-2.0.

A remote MCP server for monitoring website uptime and incidents. Uptime monitoring checks whether a service is reachable and working over time.

In plain words
What is it for?
It monitors uptime and incidents and publishes status updates for an Uptimepage organisation.
Why use it?
It can help identify outages and keep incident information current, although the description does not list its exact checks or controls.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit It monitors uptime and incidents and publishes status updates for an Uptimepage organisation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sergekostenchuk/ui-ux-agent-skill-system/migration-planner
Install

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.

Any agent
npx skills add sergekostenchuk/ui-ux-agent-skill-system --skill migration-planner
Clone the repo
git clone --depth 1 https://github.com/sergekostenchuk/ui-ux-agent-skill-system

Made for: Codex.

Wrote 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.

agentmods badge for migration-planner

README.md
[![agentmods](https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/migration-planner/github.svg)](https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/migration-planner)
Your own site
<a href="https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/migration-planner"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/migration-planner/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.

agentmods 80×15 button for migration-planner

Your own site · 80×15
<a href="https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/migration-planner"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/migration-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 575 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.00575
Opus 5 $0.00030 $0.00287
Sonnet 5 $0.00012 $0.00115
Haiku 4.5 $0.00006 $0.00057

Measured 10d ago against content hash e66cb7f6cf08, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

migration-planner 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 10d 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.

core/skills/migration-planner/SKILL.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Migration Planner

This skill creates a rollback-aware migration plan for existing sites. It is planning and validation-first, not a production mutation tool.

Operating Modes

  • url-map: map old URLs to new URLs and identify canonical decisions.
  • redirect-plan: plan 301/302 rules without applying them.
  • seo-surface: preserve titles, descriptions, headings, schema, sitemap, robots, llms.txt, and internal links.
  • launch-checklist: define pre-launch, launch, and post-launch verification.
  • rollback: prepare rollback, monitoring, and alert criteria.

Required Workflow

  1. Read references/migration-safety-contract.md.
  2. Start from existing-site-analyzer evidence and rebuild-or-improve-advisor decision.
  3. Use assets/migration-plan.template.md.
  4. Build a URL/change map:
    • old URL;
    • new URL;
    • status;
    • redirect type;
    • canonical rule;
    • metadata/schema preservation note.
  5. Add sitemap, robots, schema, internal links, llms.txt, analytics, and webmaster verification checks.
  6. Mark production actions as Planned until the user explicitly approves deploy, DNS, redirects, GSC/webmaster, or server changes.

Safety Rules

  • Do not apply redirects, edit robots/sitemap in production, deploy, change DNS, or submit GSC/webmaster changes without explicit approval.
  • Do not store private analytics exports, tokens, cookies, or verification codes in the plan.
  • Do not mark migration checks Ran unless the command or artifact exists.
  • If high SEO risk remains, block launch handoff until rollback and monitoring are defined.

Handoff Shape

Migration mode:
Decision source:
URL map path:
Redirect plan:
SEO surface preservation:
Launch approvals needed:
Rollback plan:
Monitoring:
Next owner:
Checks:

Validation

When editing this skill, run:

python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/migration-planner
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/migration-planner
python3 -m json.tool $CODEX_HOME/skills/migration-planner/evals/evals.json >/dev/null

Read the full file on GitHub · 64 lines

Files

What ships with it

4 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.

Changes

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.

  1. 10d ago First seen · 64 lines · 61 tokens per session scan A e66cb7f6cf08

Subscribe to this mod's changes

migration-planner is a skill published in the GitHub repository sergekostenchuk/ui-ux-agent-skill-system (23 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 575 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens