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/setup_codeopsnpx skills add blendsdk/claude-codeops --skill setup_codeopsgit 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.00210 | $0.01285 |
| Opus 5 | $0.00105 | $0.00642 |
| Sonnet 5 | $0.00042 | $0.00257 |
| Haiku 4.5 | $0.00021 | $0.00128 |
Grade A, and why
setup_codeops 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeOps Layout Setup (setup_codeops)
CodeOps Skills Version: 3.20.0
Set up the CodeOps nested codeops/ layout for the git repo the user is currently in. Run as
/codeops:setup_codeops or the typeable alias /setup_codeops. This is the one skill that
creates and owns the layout marker codeops/.codeops.yml; every other skill only reads it.
Resolve all paths and the marker schema via _shared/layout-convention.md — it is the single source of truth for the layout. Do not re-encode paths here.
Scope
- Per-repo only. One git repo at a time; no cross-repo or portfolio-of-projects work.
- This skill sets up the structure. It never authors requirements, plans, or roadmaps — that is
make_requirements/make_plan/roadmap, which then resolve paths via the convention doc.
Dispatch — detect repo state, then branch
Run inside the repo and detect, in this order:
1. codeops/.codeops.yml present
→ already set up. NO-OP for the layout: print a short status report (layout = nested, where
things live). BUT if the marker is **missing `integrationBranch`**, BACKFILL it — add that
one line (resolved to the repo's integration branch: `origin/HEAD`, else the current branch,
else `main`/`master`) without touching any other key; if it is already present, leave it.
Never re-scaffold or re-migrate. (Idempotent — a marker that is present and complete → no
change; this is the existing-project entry point for parallel-agents support.)
2. Flat layout detected (requirements/ OR plans/00-roadmap.md OR any plans/<dir>/)
→ MIGRATE. Follow migration.md: run the engine --dry-run, render the preview, take ONE
confirmation, then apply. The engine (scripts/codeops-migrate.sh) owns the algorithm.
3. Neither
→ fresh SCAFFOLD. Follow scaffold.md: create the minimal codeops/ skeleton.
If the repo is not a git repo, refuse with a clear message (migration needs git mv; even a
fresh scaffold should live in version control) and suggest git init first.
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.
- yesterday First seen · 82 lines · 210 tokens per session scan A cde5476a0d31
setup_codeops is a skill published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 210 tokens to every session and 1,285 once invoked, about $0.0011 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…