Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Mathews-Tom/armory --skill opus-4-7-migrationgit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mathews-tom/armory/opus-4-7-migration)<a href="https://agentmods.dev/skills/mathews-tom/armory/opus-4-7-migration"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/opus-4-7-migration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mathews-tom/armory/opus-4-7-migration"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/opus-4-7-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 160 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 161 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00044 | $0.01959 |
| Opus 5.5 | $0.00018 | $0.00784 |
| Sonnet 5.5 | $0.00009 | $0.00392 |
| Haiku 4.5 | $0.00004 | $0.00196 |
Grade A, and why
opus-4-7-migration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Opus 4.7 Migration Scanner
DEPRECATED — Retired from the active skill catalog. This package is retained under
archive/skills/opus-4-7-migration/for historical reference only and receives no further updates. The scanner and migration guidance below describe its archived behavior, not a maintained migration workflow.
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
| File | Contents | Load When |
|---|---|---|
scripts/scan.py |
Repo scanner producing a categorized findings report | Always |
references/migration-map.md |
Per-category migration actions with before/after code samples | When 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 insidethinking={...}dict literals.thinking.budget_tokensattribute references
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago Changed · +3 lines · -101 tokens per session c9b01abd9afc
- 14d ago Changed 88520fefd4b2
- 1mo ago First seen · 162 lines · 145 tokens per session scan A ed6ddd6d58bc
opus-4-7-migration is a skill published in the GitHub repository Mathews-Tom/armory (337 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,959 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
it-ram-doctor
Process tails that hold memory for nothing: finds them and, on the owner's word, kills them. Use on "slow", "swap", "low memory", "kill the tails", "clean up memory", "ram doctor", and after closing heavy apps.
review-with-dora
Use when reviewing agent context (SKILL.md, plugin, rule, AGENTS.md) with dora before reporting done. Also when ask-dora routes a Dora job (review, fix, unused, scan), or the user asks to review, diagnose, or clean up Claude, Cursor, Codex, Copilot, or Grok context.
qa-to-engineering-brief
Converts bug reports, screenshots, user panic, QA notes, and vague complaints into durable engineering briefs. Use when turning observed failures into reproducible issues with severity, expected behaviour, evidence, scope, owner, and acceptance tests.
gke-workload-scaling-troubleshooting
Diagnoses GKE HorizontalPodAutoscaler (HPA) failures — metrics showing as , FailedGetResourceMetric / FailedGetScale / FailedComputeMetricsReplicas events, missing Pod resource requests, custom/external metrics-pipeline breakage (FailedGetExternalMetric / FailedGetCustomMetric, unavailable metrics adapter…
comet-hotfix
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.