migration-guide

migration-guide is a skill for Codex from jeremylongworth-source/AgentSkills. It costs 49 tokens per session (275 once invoked), scanned A, original, MIT.

A guide for helping people move between software versions, APIs, packages, hosts, setups, or workflows when changes may break existing use. It explains required work, checks, known issues, and fallback options.

In plain words
What is it for?
Use it to write upgrade instructions, explain API or package changes, document repository restructures, add verification checks, and describe rollback or support paths.
Why use it?
It makes breaking changes visible and reduces the risk of failed upgrades, lost data, downtime, or unclear recovery steps. It also distinguishes required changes from optional improvements.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it to write upgrade instructions, explain API or package changes, document repository restructures, add verification checks, and describe rollback or support paths.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeremylongworth-source/agentskills/migration-guide
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 jeremylongworth-source/AgentSkills --skill migration-guide
Clone the repo
git clone --depth 1 https://github.com/jeremylongworth-source/AgentSkills

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-guide

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/migration-guide/github.svg)](https://agentmods.dev/skills/jeremylongworth-source/agentskills/migration-guide)
Your own site
<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/migration-guide"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/migration-guide/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-guide

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/migration-guide"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/migration-guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 275 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.00049 $0.00275
Opus 5.5 $0.00020 $0.00110
Sonnet 5.5 $0.00010 $0.00055
Haiku 4.5 $0.00005 $0.00028

Measured 1mo ago against content hash f86b618ea941, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

migration-guide 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.

skills/migration-guide/SKILL.md · 43 lines

What it actually says

Migration Guide

Core Workflow

  1. Identify source version, target version, audience, breaking changes, and migration deadline.
  2. Separate required changes from optional improvements.
  3. Provide step-by-step migration instructions with verification after each risky step.
  4. Include compatibility notes, rollback path, known issues, and support path.
  5. Preserve platform/vendor alternatives when the project is vendor-neutral.
  6. Flag unknowns, unsupported paths, and user-specific decisions.

Safety Rules

  • Do not invent compatibility, deprecation, or rollback guarantees.
  • Do not hide data loss, downtime, security, or breaking-change risks.
  • Do not provide destructive migration commands without review and backups.

Deliverable Shape

For migration guides, provide:

  • Who must migrate
  • Source and target versions
  • What changed
  • Required steps
  • Verification checks
  • Rollback or fallback path
  • Known issues
  • Support or escalation path

References

  • Read references/migration-guide-checklist.md when writing or reviewing migration guidance.
Files

What ships with it

2 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. 1mo ago First seen · 43 lines · 49 tokens per session scan A f86b618ea941

Subscribe to this mod's changes

migration-guide is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 49 tokens to every session and 275 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories

idd-spec-audit

Semantic audit of the IDD instruction corpus for leaked session context, cross-file contradictions, fresh-memory completability gaps, automation blockers, and restatement-discipline drift. Use on request to audit .github/instructions, the issue-authoring skill bundle, and the installed agent entry files (CLAUDE.md…

kurone-kito/idd-skill · 94 tokens

unity-yaml-format

Inspect, explain, diff, and carefully edit Unity text-serialized files such as .unity, .prefab, .asset, and related YAML-based project files. Use when mapping class IDs and fileIDs, tracing object references, reviewing merge conflicts, or making minimal safe edits to existing UnityYAML documents.

sator-imaging/suggest-skills · 67 tokens

authos-rbac-control

Manage AuthOS organization members, roles, invitations, SCIM tokens, and capability-based permissions. Use when implementing team administration, custom roles, service access grants, invitation flows, SCIM provisioning, or authorization checks inside an AuthOS tenant.

drmhse/authos_skill · 54 tokens

authos-service-management

Manage AuthOS tenant services, OAuth client credentials, redirect URIs, device activation URIs, plans, API keys, SAML settings, and checkout. Use when creating or configuring applications inside an AuthOS organization.

drmhse/authos_skill · 48 tokens

authos-platform-deployment

Deploy and configure an AuthOS API instance from source or Docker. Use when setting database backend, JWT signing keys, environment variables, billing provider, SMTP, GeoIP, Docker images, health checks, or production reverse proxy settings.

drmhse/authos_skill · 52 tokens

tester

Run end-to-end web quality audits with Playwright and Lighthouse using existing project scripts first. Use when the user says /tester, e2e test, smoke test, Playwright audit, Lighthouse audit, performance audit, accessibility audit, dark mode audit, mobile audit, or asks for 100/100 Lighthouse improvement guidance.

erikfiala/e2e-tester · 67 tokens