claude-opus-4-5-migration

Migrate Claude model identifiers to Opus 4.5 across Anthropic, Bedrock, Vertex AI, and Azure.

Updated Aug 23, 2026

Search Tags:#anthropic #bedrock #vertex ai #azure ai foundry #prompt updates #ai model migration #effort parameter

Ready to run

npx skills add https://github.com/stellarone/evaluate --skill claude-opus-4-5-migration-stellarone

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: claude-opus-4-5-migration
Source: https://github.com/stellarone/evaluate/tree/main/.agents/skills/claude-opus-4-5-migration
Command: npx skills add https://github.com/stellarone/evaluate --skill claude-opus-4-5-migration-stellarone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you migrate your existing Claude Sonnet/Opus prompts and model/API strings to Opus 4.5 so your application keeps working as expected with the newer model.

Core Features & Use Cases

Model string replacement: Updates Anthropic, AWS Bedrock, Vertex AI, and Azure AI Foundry model identifiers from Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5.
Known model-compatibility cleanup: Removes unsupported beta headers (including the specified 1M context beta) and flags what was changed.
Optional prompt behavior adjustments: Applies targeted prompt snippet fixes only when you explicitly request them or report issues (e.g., tool overtriggering, over-engineering, code exploration, frontend aesthetic quality, or “thinking” sensitivity).

Quick Start

Ask the Skill to migrate your codebase from Sonnet 4.5 or Opus 4.1 to Opus 4.5 and ensure it updates all model strings and records a summary of the changes made.

Frequently Asked Questions about claude-opus-4-5-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate Claude Sonnet prompts to Opus 4.5?▼

Migrating Claude Sonnet prompts to Opus 4.5 requires replacing existing Anthropic API model strings with Opus 4.5 target identifiers and removing unsupported beta headers like the 1M context beta. This updates model identifiers across AWS Bedrock, Vertex AI, and Azure AI Foundry for application compatibility.

Does Opus 4.5 migration support AWS Bedrock and Vertex AI model strings?▼

Yes, Opus 4.5 migration supports AWS Bedrock, Google Vertex AI, Azure AI Foundry, and Anthropic 1P API model string updates. It specifically replaces Sonnet 4.0, Sonnet 4.5, and Opus 4.1 source identifiers with the correct Opus 4.5 target strings across these platforms.

What beta headers need to be removed when upgrading to Opus 4.5?▼

When upgrading to Opus 4.5, you must remove unsupported beta headers, specifically including the 1M context beta header. The migration process flags all changed headers and model strings, providing a summary of modifications to ensure the application behaves as expected.

Can I add effort parameter configuration when migrating to Opus 4.5?▼

Yes, you can optionally add effort parameter configuration guidance for high effort when migrating to Opus 4.5. This optional adjustment is applied alongside mandatory model string replacements to help tune Opus 4.5 behavior for specific application needs.

How do I fix prompt behavior issues like tool overtriggering after an Opus 4.5 model update?▼

To fix prompt behavior issues like tool overtriggering after an Opus 4.5 model update, you can apply targeted prompt snippet fixes. These optional behavior adjustments address over-engineering, code exploration, frontend aesthetic quality, and thinking sensitivity only when explicitly requested.

What are the limitations of migrating Claude models to Opus 4.5?▼

A key limitation of migrating Claude models to Opus 4.5 is that it explicitly avoids Haiku migrations, focusing only on Sonnet 4.0/4.5 and Opus 4.1 sources. Additionally, optional behavior fixes are only applied when you explicitly request them or report specific issues.