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/make_plannpx skills add blendsdk/claude-codeops --skill make_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.00126 | $0.03964 |
| Opus 5 | $0.00063 | $0.01982 |
| Sonnet 5 | $0.00025 | $0.00793 |
| Haiku 4.5 | $0.00013 | $0.00396 |
Grade A, and why
make_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 yesterday.
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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Plan Creation (make_plan)
Create a detailed, multi-document implementation plan for a software feature or task. This skill covers plan creation only. To execute a finished plan, use the exec_plan skill.
CodeOps Skills Version: 3.20.0
What you produce
A folder plans/<feature-name>/ containing:
plans/<feature-name>/
├── 00-ambiguity-register.md # Zero-Ambiguity Gate register (audit trail)
├── 00-index.md # Overview and navigation
├── 01-requirements.md # Requirements and scope
├── 02-current-state.md # Current implementation analysis
├── 03-XX-<component>.md # Technical spec per component (one or more)
├── 07-testing-strategy.md # Spec test cases + verification
└── 99-execution-plan.md # Phases, sessions, task checklist
The full templates for every document live in templates.md — read it before writing any plan document in Phase 2.
Resolve paths first (layout-aware)
Determine the layout via ../../_shared/layout-convention.md before creating the plan folder:
- Flat layout (no marker): the plan folder is
plans/<feature-name>/;00-index.mddeclares> **Implements**: RD-NN— exactly as flat layout always has. - Nested layout (marker present): the plan folder is
codeops/features/<f>/plans/<plan>/. Ask/confirm the target feature first (create the feature folder lazily if new — never guess).00-index.mddeclares a feature-qualified> **Implements**: <feature>/RD-NN, and any> **Source**link points at the feature's ownrequirements/dir. Everywhere below that saysplans/<feature-name>/means this nested plan path.
Lightweight tasks (mini-plan path — both layouts)
Not every change is a feature. Ad-hoc work (a bugfix, chore, small change) is a task (T-NN), and a non-trivial task gets a single mini-plan, not the full multi-document set. When the work is a task (see the routing rule in ../../_shared/layout-convention.md):
What ships with it
3 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.
- yesterday First seen · 210 lines · 126 tokens per session scan A d3127b67bad0
make_plan is a skill published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 126 tokens to every session and 3,964 once invoked, about $0.0006 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…