claude-opus-4-5-migration

Migrate model strings and prompts from Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/ace8991/agentos --skill claude-opus-4-5-migration-ace8991
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-opus-4-5-migration
Source: https://github.com/ace8991/agentos/tree/main/.tmp_claude_code/claude-code-main/plugins/claude-opus-4-5-migration/skills/claude-opus-4-5-migration
Command: npx skills add https://github.com/ace8991/agentos --skill claude-opus-4-5-migration-ace8991

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Upgrading a codebase to Claude Opus 4.5 requires finding every model string across multiple platforms (Anthropic API, AWS Bedrock, Google Vertex AI, Azure AI Foundry), removing unsupported beta headers, and adjusting prompts for known behavioral differences. Doing this manually is error-prone and easy to miss edge cases. ## Core Features & Use Cases - Model String Migration: Detects and replaces Sonnet 4.0, Sonnet 4.5, and Opus 4.1 model strings with the correct Opus 4.5 identifier for each platform, while explicitly leaving Haiku models untouched. - Beta Header Cleanup: Removes the unsupported context-1m-2025-08-07 beta header and optionally adds the effort parameter set to high via the effort-2025-11-24 beta flag. - Prompt Adjustments for Behavioral Differences: Provides targeted fixes for tool overtriggering, over-engineering, insufficient code exploration, generic frontend design, and sensitivity to the word "think" when extended thinking is disabled. - Use Case: You have a production application calling claude-sonnet-4-5-20250929 through AWS Bedrock. This Skill updates the model string to the Bedrock Opus 4.5 identifier, adds the effort parameter, and softens aggressive tool-triggering language in your system prompt. ## Quick Start Migrate my codebase from Claude Sonnet 4.5 to Opus 4.5, updating all model strings and API calls.

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 my code from Claude Sonnet 4.5 to Opus 4.5?

Search your codebase for the Sonnet 4.5 model string and replace it with the Opus 4.5 identifier for your platform, such as claude-opus-4-5-20251101 for the Anthropic API. Also remove the unsupported context-1m-2025-08-07 beta header and consider adding the effort parameter set to high.

What is the Opus 4.5 model string for AWS Bedrock and Vertex AI?

On AWS Bedrock use anthropic.claude-opus-4-5-20251101-v1:0, and on Google Vertex AI use claude-opus-4-5@20251101. The Anthropic first-party API and Azure AI Foundry both use claude-opus-4-5-20251101.

Does the Opus 4.5 migration also update Haiku models?

No, this migration explicitly does not touch Haiku models such as claude-haiku-4-5-20251001. Only Sonnet 4.0, Sonnet 4.5, and Opus 4.1 model strings are replaced with Opus 4.5 equivalents.

Why is Claude Opus 4.5 calling tools too frequently?

Opus 4.5 is more responsive to system prompts, so aggressive language like CRITICAL, MUST, or ALWAYS that prevented undertriggering on older models now causes overtriggering. Soften these phrases to normal phrasing such as "Use this tool when..." in tool-triggering instructions only.

How do I configure the effort parameter for Opus 4.5?

Add the beta flag effort-2025-11-24 to your API request and set output_config.effort to high, medium, or low. High effort is the recommended default for best performance, while low effort suits simple high-volume queries.

Why does Opus 4.5 behave oddly when my prompt says "think"?

When extended thinking is not enabled, Opus 4.5 is sensitive to the word "think" and its variants. Replace phrases like "think about" with "consider" or "evaluate" unless your API request includes a thinking parameter enabling extended thinking.