Error Debugging
Security scan passedTwo debugging subagents and three commands that find the root cause of errors, set up error tracking and run multi-agent code reviews.

Has your agent move code and prompts from Sonnet 4.x or Opus 4.1 to Claude Opus 4.5, from model strings to prompt fixes.
by Anthropic· AI & agentsUnclaimed · Yours? Claim it
About
Anthropic's own Claude Code plugin for moving a codebase from Claude Sonnet 4, Sonnet 4.5 or Opus 4.1 to Claude Opus 4.5. It's a single skill: ask your agent to migrate, and it finds your model strings and API calls, updates them and sums up what it changed. What it does - Searches your codebase for model strings and API calls - Swaps in the Opus 4.5 model string for the Claude API, AWS Bedrock, Google Vertex AI or Azure AI Foundry - Removes the 1M-context beta header, which the skill says Opus 4.5 doesn't support yet, and leaves a comment saying why - Adds the effort parameter, set to high - Lists every change it made Prompt fixes, only when you ask Opus 4.5 behaves differently from earlier models, so the skill carries fixes for known issues. By default it only updates model strings; it applies these when you ask or report the problem: - Tools called too often: it softens forceful wording such as "CRITICAL" or "You MUST" in tool instructions - Extra files and abstractions: it adds a snippet that keeps solutions minimal - Fixes proposed without reading the code: it adds a snippet that has the model read the files first - Generic-looking frontend output: it adds a frontend design snippet - Trouble with the word "think" when extended thinking is off: it swaps in words like "consider" or "evaluate" How to install it In Claude Code, run /plugin marketplace add anthropics/claude-code, then /plugin install claude-opus-4-5-migration@claude-code-plugins. Then ask "Migrate my codebase to Opus 4.5". Good to know - It leaves Haiku models alone. - It targets Opus 4.5 only, not newer Claude models. - If anything feels off after the move, keep using the skill to adjust your prompts.
Plugins people install alongside Claude Opus 4.5 Migration.
4 images
Once it’s added
“Migrate my codebase to Opus 4.5.”
“Update our Bedrock model IDs to Opus 4.5.”
“Opus 4.5 keeps calling tools it doesn't need. Can you adjust our prompts?”
“Since the switch it adds files and abstractions we didn't ask for. Fix the prompt.”
“It proposes fixes without reading the code first. Update our system prompt.”
“Our frontend output looks generic. Improve the design prompt.”
Before you add it
Reads only
Searches your codebase for Claude model strings and API calls
Makes changes · your agent can ask first
Updates model strings to Opus 4.5 and removes the unsupported beta header · Adds the effort parameter, set to high · Edits your prompts, only when you ask or report an issue
From people who use it
Step by step
Nothing new reaches your agent until a person has looked at it.
Scanned on every change, and again when our rules improve.
Runs on your machine.
Runs on your machine.
/plugin marketplace add anthropics/claude-code /plugin install claude-opus-4-5-migration@claude-code-plugins
Scanned and passed · checked 7 days ago
No reviews yet. Used Claude Opus 4.5 Migration? Say how it went.
Write a reviewNobody has shared how they use Claude Opus 4.5 Migration yet.
Security scan
Passed
Safe to install in every agent it supports. Claude plugins.
Plugins people install alongside Claude Opus 4.5 Migration.
Two debugging subagents and three commands that find the root cause of errors, set up error tracking and run multi-agent code reviews.
ByteDance's local MCP server that lets your agent run any shell command or script on your machine, with your own permissions.
Keeps your agent's plan, findings and progress in markdown files on disk, so long tasks survive /clear, crashes and compaction.