New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Opus 4 7 Migration

by Mathews-Tom in Mathews-Tom/armory

Scan a repository for Opus-4.6-era patterns that break or degrade on Opus 4.7 — fixed-budget Extended Thinking parameters, retired model ID aliases, and prompts that assumed verbose default output…

MITAuto-check: notesAgent Workflows

Install Opus 4 7 Migration

skills CLI
$ npx skills add Mathews-Tom/armory --skill opus-4-7-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Mathews-Tom/armory opus-4-7-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/opus-4-7-migration .claude/skills/opus-4-7-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
opus-4-7-migration
GitHub stars
328
Token cost
~2.1k tokens
SKILL.md length
799 words
Files
6 (incl. scripts, references)
Skills in repo
80
Repo updated
First seen
Licence
MIT

At a glance

Scan a repository for Opus-4.6-era patterns that break or degrade on Opus 4.7 — fixed-budget Extended Thinking parameters, retired model ID aliases, and prompts that assumed verbose default output…

  • Works in 3 steps: Run the Scanner → Triage Findings → Write the Migration PR
  • : opus 4.7 migration
  • SKILL.md covers Reference Files, When to Run, Scope — What the Scanner Flags and Workflow, plus 4 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Opus 4 7 Migration is an agent skill from Mathews-Tom/armory. Scan a repository for Opus-4.6-era patterns that break or degrade on Opus 4.7 — fixed-budget Extended Thinking parameters, retired model ID aliases, and prompts that assumed verbose default output or eager sub-agent delegation. Produces a categorized report with file:line references and migration actions. Triggers on: "opus 4.7 migration", "migrate to opus 4.7", "audit for opus 4.7", "opus 4.6 to 4.7", "scan for budgettokens", "find retired model IDs", "adapt repo to opus 4.7". NOT for implementing migrations —…

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `evals/cases.yaml`, `references/migration-map.md` and `scripts/scan.py`).

It sits in Agent Workflows, covering Subagents. The repository describes itself as: Curated, production-grade skills for AI coding agents. Battle-tested workflows for developers who use AI seriously. The licence is MIT.

When your agent uses it

  • : opus 4.7 migration
  • Migrate to opus 4.7
  • Audit for opus 4.7
  • Opus 4.6 to 4.7

Example prompts

  • “opus 4.7 migration”
  • “migrate to opus 4.7”
  • “audit for opus 4.7”
  • “/opus-4-7-migration”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Run the Scanner
  2. Triage Findings
  3. Write the Migration PR

What it can do on your machine

Read from SKILL.md and the folder at commit 4594fb7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Opus 4 7 Migration loads about 2.1k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 143 tokens; SKILL.md has 799 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~143
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:57
    ` source code outside of `config.toml`, `.env`, or test-only sentinel strings is a candidate for extraction.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from Mathews-Tom/armory at commit 4594fb7, republished under its MIT licence (© Mathews-Tom). 799 words, ~2,119 tokens.

Download SKILL.mdSave it as .claude/skills/opus-4-7-migration/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
opus-4-7-migration
description
Scan a repository for Opus-4.6-era patterns that break or degrade on Opus 4.7 — fixed-budget Extended Thinking parameters, retired model ID aliases, and prompts that assumed verbose default output or eager sub-agent delegation. Produces a categorized report with file:line references and migration actions. Triggers on: "opus 4.7 migration", "migrate to opus 4.7", "audit for opus 4.7", "opus 4.6 to 4.7", "scan for budget_tokens", "find retired model IDs", "adapt repo to opus 4.7". NOT for implementing migrations — this skill identifies candidates.
metadata.version
1.0.0
metadata.category
review
metadata.tags
opus-4-7, migration, audit, model-refresh, budget-tokens
metadata.difficulty
intermediate
metadata.phase
review

Opus 4.7 Migration Scanner

Identify patterns in a repository that break or silently degrade when the Anthropic platform routes to Opus 4.7. Produces a categorized report with file:line references so a maintainer can plan a scoped migration PR rather than chasing symptoms after the fact.

Reference Files

FileContentsLoad When
scripts/scan.pyRepo scanner producing a categorized findings reportAlways
references/migration-map.mdPer-category migration actions with before/after code samplesWhen a category returns findings

When to Run

  • Before upgrading a service or agent stack to Opus 4.7
  • When an existing Anthropic SDK integration starts returning errors after the platform rolled out 4.7
  • Periodically in a CI or weekly audit to prevent drift as the repo grows
  • Before publishing a package that downstream users will run against 4.7

Scope — What the Scanner Flags

The scanner is intentionally narrow. It reports three categories of deterministic patterns plus two heuristic categories that require manual review.

Category A — Fixed-budget Extended Thinking (deterministic)

Opus 4.7 does not support Extended Thinking with a fixed budget_tokens value. Code that still passes thinking={"type": "enabled", "budget_tokens": N} fails or is ignored depending on SDK version.

Patterns flagged:

  • Literal budget_tokens= in Python source
  • "budget_tokens" keys inside thinking={...} dict literals
  • .thinking.budget_tokens attribute references
Category B — Retired model ID aliases (deterministic)

Dated or superseded Claude model aliases that no longer map to the current model. Using them is not broken but defeats the platform's model routing.

Patterns flagged:

  • claude-opus-4-5, claude-opus-4-4, claude-opus-4-3, claude-opus-4-2, claude-opus-4-1, claude-opus-4-0
  • claude-sonnet-4-5, claude-sonnet-4-4, claude-sonnet-4-3, claude-sonnet-4-2, claude-sonnet-4-1, claude-sonnet-4-0
  • Dated format aliases: claude-*-20250514, claude-*-20241022, etc.
  • claude-3-* family (superseded)
Category C — Hardcoded model references outside config (deterministic)

Per the armory convention "model refs in config files only," any claude-* literal in .py / .ts / .js source code outside of config.toml, .env, or test-only sentinel strings is a candidate for extraction.

Category D — Opus-4.6-verbosity-assuming prompts (heuristic)

Opus 4.7 is less default-verbose than 4.6. Prompts that relied on Opus 4.6's eager output or never needed a depth cue may produce shorter-than-expected responses on 4.7.

Patterns flagged (review required):

  • Prompts requesting "detailed" or "comprehensive" output without matching length directive
  • Prompts that exceeded Opus 4.6's defaults by relying on implicit verbosity
  • Absence of first-turn specification completeness in agent prompts
Category E — Non-explicit parallel sub-agent dispatch (heuristic)

Opus 4.7 delegates more judiciously than 4.6. Agent prompts instructing "spawn in parallel" without the phrase "in a single message" or stating sub-task independence often serialize on 4.7.

Patterns flagged (review required):

  • Spawn + parallel language in agent prompts without "single message" or "independent"
  • subagent_type dispatches in loops or sequential blocks where parallelism was intended

Workflow

Phase 1: Run the Scanner

Execute:

bash
python3 scripts/scan.py /path/to/repo

Optional flags:

  • --categories A,B,C — run only deterministic categories (skip heuristics)
  • --exclude tests/,vendor/,node_modules/ — path exclusion
  • --format json — machine-readable output for CI integration
  • --exit-code — exit 1 if any findings (useful for pre-commit hooks)
Show full SKILL.md (339 more words)Show less
Phase 2: Triage Findings

Group findings by category and sort by severity. Deterministic categories (A, B, C) are always actionable. Heuristic categories (D, E) require reading the surrounding prompt context before editing.

Priority order for a migration PR:

  1. Category A first — these either error out or silently do the wrong thing on 4.7
  2. Category B — rename to current logical aliases (claude-opus-4-7, claude-sonnet-4-6, claude-haiku-4-5) or to the platform's auto-routing name
  3. Category C — extract to config.toml per repo convention
  4. Category D, E — manual review; fix those that materially change behavior
Phase 3: Write the Migration PR

For each category with findings, apply the actions documented in references/migration-map.md. Prefer small PRs grouped by category over one large PR.

Pair the migration with:

  • Unit tests or integration tests that exercise the updated code paths on Opus 4.7
  • A short CHANGELOG entry noting "Opus 4.7 compatibility: removed budget_tokens from …"
  • A rollout plan if the service is production-critical (high/xhigh effort level on the targeted agents)

Output Format

The scanner produces a categorized report:

Opus 4.7 Migration Scan — /path/to/repo

Category A: Fixed-budget Extended Thinking       2 findings
  src/agent/reasoner.py:47   budget_tokens=8000
  src/agent/planner.py:112   thinking={"type": "enabled", "budget_tokens": 4096}

Category B: Retired model ID aliases             3 findings
  tests/test_agent.py:89     claude-opus-4-5
  config/dev.yaml:14         claude-sonnet-4-5
  src/llm/client.py:23       claude-sonnet-4-20250514

Category C: Hardcoded model refs outside config  1 finding
  scripts/bulk_process.py:8  DEFAULT_MODEL = "claude-sonnet-4-6"

Category D: Verbosity-assuming prompts          0 findings (heuristics disabled)
Category E: Non-explicit parallel dispatch      0 findings (heuristics disabled)

Total: 6 deterministic findings across 3 categories.

Error Handling

ConditionAction
Repo path does not existExit 2 with a clear error message
No Python / TypeScript / JS files in repoSkip Category A, C; continue with B, D, E on other file types
Regex error in scannerExit 3; file a bug with the offending pattern
False positives from Category B on changelogsExclude CHANGELOG.md by default; override with --include-changelogs

Limitations

  • Categories D and E are heuristic and will produce false positives on carefully written prompts. Review before changing.
  • The scanner does not exercise the code — it only does static pattern matching. A budget_tokens variable that is never passed to the Anthropic SDK will still be flagged.
  • The scanner cannot detect runtime dynamic model selection (e.g., model = config["models"][stage]) — those need integration tests, not static analysis.
  • Cross-language analysis is limited to Python, TypeScript, JavaScript, YAML, TOML, and Markdown. Other languages are skipped.
  • rules/adaptive-thinking-control/RULE.md — prompt-level controls that replace fixed thinking budgets
  • skills/usage-audit/SKILL.md — broader context-bloat audit (complementary)
  • skills/mcp-to-skill/SKILL.md — MCP-to-skill conversion (relevant when migration surfaces heavy MCP usage)

© Mathews-Tom, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/opus-4-7-migration of Mathews-Tom/armory.

  • SKILL.md
  • evals/cases.yaml
  • references/migration-map.md
  • scripts/scan.py
  • tests/conftest.py
  • tests/test_scan.py

Open the folder on GitHubat commit 4594fb7

Compare with similar skills

Opus 4 7 Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Opus 4 7 Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Opus 4 7 Migration this skillMathews-Tom/armory328—~2.1kAutomated safety check: NotesMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k7 repos~2.8kAutomated safety check: PassApache-2.0
Subagent Driven DevelopmentAsvarox/allkaraoke26137 repos~1.2kAutomated safety check: PassNone
Dispatching Parallel Agentsultralisp/ultralisp25840 repos~1.5kAutomated safety check: PassNone
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
Task Observerrebelytics/one-skill-to-rule-them-all3.2k1 repos~12kAutomated safety check: PassCC-BY-4.0

Similar skills

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 37 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • Dispatching Parallel Agents

    ultralisp/ultralisp

    A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    258 GitHub starsUsed in 40 repos~1.5k tokens
    Agent WorkflowsAuto-check passed

  • Paseo Advisor Second Opinion

    getpaseo/paseo

    Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed

  • Task Observer

    rebelytics/one-skill-to-rule-them-all

    Monitors task execution for skill improvement opportunities.

    3.2k GitHub starsUsed in 1 repo~12k tokens
    Agent WorkflowsAuto-check passed

  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from Mathews-Tom/armory

All 80 skills in this repo

  • Architecture Reviewer

    Mathews-Tom/armory

    Architecture reviews across 7 dimensions (structural, scalability, enterprise readiness, performance, security, ops, data) with scored reports.

    328 GitHub stars~4.6k tokensUpdated 4 days ago
    Auto-check passed

  • Concept To Image

    Mathews-Tom/armory

    Turn concepts into static HTML visuals exported as PNG or SVG files via HTML/CSS/SVG.

    328 GitHub stars~2.6k tokensUpdated 4 days ago
    Auto-check passed

  • Watch

    Mathews-Tom/armory

    A skill your agent uses when analyzing an existing video URL or local recording: "watch this video", "analyze youtube video", "summarize this video", "youtube transcript", "find this moment", "what…

    328 GitHub stars~2.8k tokensUpdated 4 days ago
    Auto-check passed

  • Code Refiner

    Mathews-Tom/armory

    Deep code simplification and refactoring preserving behavior across Python, Go, TypeScript, Rust.

    328 GitHub stars~3.1k tokensUpdated 4 days ago
    Auto-check passed

  • Concept To Video

    Mathews-Tom/armory

    Turn concepts into animated explainer videos using Manim (Python) with MP4/GIF output, audio overlay, multi-scene composition.

    328 GitHub stars~4.9k tokensUpdated 4 days ago
    Auto-check passed

  • Decision Map

    Mathews-Tom/armory

    Maps the unresolved architecture, policy, and scope decisions that must be answered before planning can start: one durable decision ticket per question on the issue tracker, typed and blocker-linked…

    328 GitHub stars~2.7k tokensUpdated 4 days ago
    Auto-check passed

Categories

Questions about Opus 4 7 Migration

What does Opus 4 7 Migration do?

Scan a repository for Opus-4.6-era patterns that break or degrade on Opus 4.7 — fixed-budget Extended Thinking parameters, retired model ID aliases, and prompts that assumed verbose default output…. Opus 4 7 Migration is an agent skill from Mathews-Tom/armory.7 — fixed-budget Extended Thinking parameters, retired model ID aliases, and prompts that assumed verbose default output or eager sub-agent delegation.

When should I use Opus 4 7 Migration?

Opus 4 7 Migration fits situations like: : opus 4.7 migration; migrate to opus 4.7; audit for opus 4.7; opus 4.6 to 4.7.

How do I install Opus 4 7 Migration in Claude Code?

Run `npx skills add Mathews-Tom/armory --skill opus-4-7-migration -a claude-code`. Or copy the skill folder (skills/opus-4-7-migration in Mathews-Tom/armory) into .claude/skills/opus-4-7-migration in your project. Claude Code loads it when a task matches its description.

How do I install Opus 4 7 Migration in Codex?

Run `npx skills add Mathews-Tom/armory --skill opus-4-7-migration -a codex`. Or copy the skill folder (skills/opus-4-7-migration in Mathews-Tom/armory) into .agents/skills/opus-4-7-migration in your project. Codex loads it when a task matches its description.

Can I use Opus 4 7 Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mathews-Tom/armory --skill opus-4-7-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/opus-4-7-migration, .gemini/skills/opus-4-7-migration, .github/skills/opus-4-7-migration and .opencode/skills/opus-4-7-migration in your project.

What does Opus 4 7 Migration need to run?

Going by SKILL.md and its folder, Opus 4 7 Migration needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Opus 4 7 Migration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Opus 4 7 Migration safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Opus 4 7 Migration use?

Opus 4 7 Migration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Opus 4 7 Migration use?

About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Opus 4 7 Migration?

Skills that share tags, products or a category with Opus 4 7 Migration: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Opus 4 7 Migration?

Mathews-Tom (a GitHub user) maintains it in Mathews-Tom/armory, which has 328 GitHub stars. The repository holds 80 skills in this directory. The repository was last updated on October 6, 2026.

Source: Mathews-Tom/armory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.