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 agentmods add skills/blendsdk/claude-codeops/upgrade_plannpx skills add blendsdk/claude-codeops --skill upgrade_plangit clone --depth 1 https://github.com/blendsdk/claude-codeopsWhat 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 | $0.00178 | $0.02766 |
| Opus 5 | $0.00089 | $0.01383 |
| Sonnet 5 | $0.00036 | $0.00553 |
| Haiku 4.5 | $0.00018 | $0.00277 |
Grade A, and why
upgrade_plan 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 3d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
upgrade_plan — Upgrade a Plan or Requirements Set
CodeOps Skills Version: 3.20.0
Plans and requirements are living documents. As CodeOps standards evolve, older artifacts drift out of date. This skill detects staleness, assesses gaps against current standards, upgrades documents while preserving all user-authored content, and verifies the result.
This skill covers upgrades only. To create a new plan use the make_plan skill; to create a new requirements set use the make_requirements skill.
Resolve paths layout-aware, and don't migrate layout here. A plan/requirements set lives at a flat path (
plans/<feature>/,requirements/) or, in a nested-layout repo, undercodeops/features/<f>/…— resolve it via ../../_shared/layout-convention.md. This skill upgrades content/version in place; it never moves a repo between layouts. Converting a flat repo to the nestedcodeops/layout is thesetup_codeopsskill's job — point the user there for that, and keep upgrades within the existing layout.
Which target? (branch first)
Detect the target from the phrasing/arguments before doing anything else:
| Trigger | Target | Directory |
|---|---|---|
upgrade_plan [feature-name], "upgrade my plan", "bring the plan up to date" |
Plan | plans/[feature-name]/ |
upgrade_requirements, "upgrade my requirements", "bring requirements up to date" |
Requirements | requirements/ |
If the target is genuinely ambiguous (e.g. bare "upgrade"), ask the user which one. The two branches share the same 4-phase flow; the per-document checklists differ and live in upgrade-checklists.md.
Version detection & classification
- Read the plan's
00-index.md(or99-execution-plan.md), or for requirements theREADME.mdand individual RD documents. - Look for a version stamp:
> **CodeOps Version**: X.Y.Zor> **CodeOps Skills Version**: X.Y.Z. - Compare the stamp against the current standard version 3.3.2 (the bumps since
3.0.0are behavioral — no document migration — so3.0.0–3.3.1artifacts remain compatible).
What ships with it
2 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.
- 3d ago First seen · 218 lines · 178 tokens per session scan A b478caa68a41
upgrade_plan is a skill published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 178 tokens to every session and 2,766 once invoked, about $0.0009 per session on Opus 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…