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/roadmapnpx skills add blendsdk/claude-codeops --skill roadmapgit 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.00250 | $0.05479 |
| Opus 5 | $0.00125 | $0.02740 |
| Sonnet 5 | $0.00050 | $0.01096 |
| Haiku 4.5 | $0.00025 | $0.00548 |
Grade A, and why
roadmap 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
roadmap — Live Feature-Set Roadmap Keeper
CodeOps Skills Version: 3.20.0
Resolve paths first (layout-aware)
Before any action, determine the layout via ../../_shared/layout-convention.md:
- Flat layout (no
codeops/.codeops.yml): a single roadmap atplans/00-roadmap.md. Behaves exactly as flat layout always has — everything below that mentions "the roadmap" means this one file, and the portfolio tier does not exist (its cascade steps are inert). - Nested layout (marker present): two tiers — a per-feature roadmap at
codeops/features/<f>/00-roadmap.mdand a portfolio roadmap atcodeops/00-roadmap.md(one row per feature, auto-cascaded). In nested layout the skill asks/confirms the target feature before acting on a per-feature roadmap, and creates the feature folder lazily (never guesses).
The roadmap is a living document that tracks an entire feature at a higher altitude than any
individual execution plan. Where 99-execution-plan.md tracks the tasks within one feature, the
roadmap tracks every requirement (RD), plan, and task and the lifecycle stage each is in. It is
the user's cross-session lifeline: open it to see what is done, in flight, blocked, or in backlog.
It never replaces the execution plan; it indexes and summarizes across many of them.
Action dispatch
Detect the action from the user's phrasing or argument and branch:
| Trigger | Action |
|---|---|
make_roadmap, "create the roadmap", "start a roadmap" |
make — create + seed |
update_roadmap, "sync the roadmap", "update the roadmap" |
update — re-infer + sync |
review_roadmap, "check the roadmap", "is the roadmap healthy" |
review — read-only health check |
show_roadmap, "show the roadmap", "roadmap status", "where do things stand", "what's the progress on " |
show — read-only status overview |
archive_roadmap, "archive the feature-set", "archive the roadmap" |
archive — move to _archive |
compact_roadmap, "compact the roadmap", "clean up / slim the roadmap" |
compact — strip the legacy Notes log + trim fat cells |
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 · 359 lines · 250 tokens per session scan A 21ffbb71a7eb
roadmap is a skill published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 250 tokens to every session and 5,479 once invoked, about $0.0013 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…