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 tomzx/agents --skill create-roadmapgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/create-roadmap)<a href="https://agentmods.dev/skills/tomzx/agents/create-roadmap"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-roadmap/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/tomzx/agents/create-roadmap"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00032 | $0.01883 |
| Opus 5.5 | $0.00013 | $0.00753 |
| Sonnet 5.5 | $0.00006 | $0.00377 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
create-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 22d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Roadmap
Defines the project's roadmap as a single context-level artifact: the initiatives the project is betting on, sequenced across horizons (Now / Next / Later) and tied to the objectives in goals.md.
Other skills consult the roadmap when deciding what to work on next.
Without a roadmap, prioritization is ad hoc: every issue is ranked in isolation, sequencing constraints are invisible, and there is no shared view of what is committed versus exploratory.
A plan (plan.md) describes how to build one feature; the roadmap describes what to build and in what order across the whole project.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. .sdlc/context/project-overview.md(must exist, for purpose and scope)..sdlc/context/goals.md(strongly recommended; every initiative aligns to an objective and key result. If absent, note that alignment cannot be checked and flag it as an open question)..sdlc/context/roadmap.md(optional; if present, revise rather than replace, per Revision Mode below).- Existing features under
.sdlc/features/and the open issue backlog (optional, to group into initiatives and detect orphaned work).
Steps
- Read
.sdlc/context/project-overview.mdfor purpose, scope, and stakeholders. - Read
.sdlc/context/goals.mdif present; these objectives anchor every initiative. Read.sdlc/context/service-levels.mdif present, for reliability constraints that bound what can be committed to Now. - Inventory in-flight and planned work: scan
.sdlc/features/and, if the backlog is in GitHub, list open issues withghx issue list --state open. - Confirm the horizon model with the user if not already stated: prefer Now / Next / Later (the default) over date-based quarters, because horizons avoid the false precision of dates. Note the current period.
- Identify the recurring themes for this period, each tied to a
goals.mdobjective. - Group work into initiatives (a coherent bet that moves a metric), not individual tickets. For each initiative capture the objective it advances, an owner, the hypothesis, scope, dependencies, confidence, and a success signal tied to a key result or KPI.
- Place each initiative in the right horizon:
- Now: committed, in-flight, or starting this horizon. Fully scoped.
- Next: planned for the following horizon. Roughly scoped.
- Later: exploratory, hypothesis-level, low confidence.
- Map sequencing and dependencies between initiatives (hard, soft, external), and render a Mermaid Gantt chart in the Timeline section visualizing the initiatives across the horizons, anchored to the current period.
Use the horizons as
sectiongroups, approximate spans (not hard dates), andafter <id>to show dependencies. - State Not Now explicitly: deferred work and the condition that would promote it.
- Record capacity and hard constraints if known (team capacity, regulatory deadlines, frozen periods).
- Set a review cadence and today's date.
- Write the output to
.sdlc/context/roadmap.md. If it already exists, revise per Revision Mode.
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.
- 22d ago Changed · +18 lines 8dc80d1bde39
- 24d ago Changed 2a7d9cde649d
- 2mo ago First seen · 106 lines · 32 tokens per session scan A ceffe74aabea
create-roadmap is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,883 once invoked, about $0.0001 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…