claude-opus-4-5-migration — Claude Code skill: move to Opus 4.5
A skill that scans your codebase for model strings and API calls and switches them to Opus 4.5. Useful when a project needs the newer model.
npx claude-code-templates@latest --skill development/claude-opus-4-5-migrationWhat claude-opus-4-5-migration does
The skill walks the repository looking for model strings and API calls, then swaps in the Opus 4.5 identifier for whichever platform you use: claude-opus-4-5-20251101 on the Anthropic API, anthropic.claude-opus-4-5-20251101-v1:0 on AWS Bedrock, claude-opus-4-5@20251101 on Google Vertex AI, claude-opus-4-5-20251101 on Azure AI Foundry. It also strips the context-1m-2025-08-07 beta header, which Opus 4.5 does not accept yet, and leaves a comment in its place.
Model strings are the only thing changed by default. Prompt rewrites happen only when you ask for them or describe a specific problem. In that case the skill pulls ready snippets from references/prompt-snippets.md and folds them into the prompt with XML tags instead of tacking them on at the end. Effort parameter setup lives in references/effort.md.
Migration runs one way: Haiku models stay untouched, and the accepted sources are Claude, Claude and Opus 4.1. At the end the skill lists everything it changed.
What it helps with
- locate every model string and API call across a repository
- swap Claude, Claude and Opus 4.1 identifiers for Opus 4.5
- drop the
context-1m-2025-08-07beta header that Opus 4.5 rejects - soften forceful prompt wording that makes tools fire too often
- fold new snippets into a prompt with XML tags without breaking its structure
Example prompts for the agent
- Move this project to Opus 4.5: find the model strings and API calls and update them
- The model calls tools too often now — soften the wording in my prompts
- Add the snippet against extra files and abstractions from
references/prompt-snippets.mdto my prompt
How to install claude-opus-4-5-migration
1claude-code-templates
npx claude-code-templates@latest --skill development/claude-opus-4-5-migration2Skills CLI (Vercel)
npx skills add davila7/claude-code-templates --skill claude-opus-4-5-migration -a claude-code3Manually: put the files in place
~/.claude/skills/claude-opus-4-5-migration/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/claude-opus-4-5-migration/
Manually: put the files in place
.agents/skills/claude-opus-4-5-migration/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/claude-opus-4-5-migration/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davila7/claude-code-templates claude-opus-4-5-migration2Manually: put the files in place
.github/skills/claude-opus-4-5-migration/SKILL.mdPlatform CLI
gemini skills install https://github.com/davila7/claude-code-templates --path cli-tool/components/skills/development/claude-opus-4-5-migrationManually: put the files in place
.devin/skills/claude-opus-4-5-migration/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about claude-opus-4-5-migration
How do I install claude-opus-4-5-migration in Claude Code?
Run npx claude-code-templates@latest --skill development/claude-opus-4-5-migration. Or use npx skills add davila7/claude-code-templates --skill claude-opus-4-5-migration -a claude-code. The skill file itself sits at ~/.claude/skills/claude-opus-4-5-migration/SKILL.md.
What does claude-opus-4-5-migration do?
It searches your codebase for model strings and API calls, replaces them with the Opus 4.5 identifier for your platform, and removes the unsupported beta header. Prompt edits happen only on request.
Can it migrate a project off Haiku?
No. Haiku is out of scope; the skill covers Claude, Claude and Opus 4.1.