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 build-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/build-roadmap)<a href="https://agentmods.dev/skills/tomzx/agents/build-roadmap"><img src="https://agentmods.dev/badge/skills/tomzx/agents/build-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/build-roadmap"><img src="https://agentmods.dev/badge/skills/tomzx/agents/build-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.00028 | $0.00459 |
| Opus 5 | $0.00014 | $0.00230 |
| Sonnet 5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
build-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 5d 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.
What it actually says
Build Roadmap
An outcome-based roadmap, not a feature delivery calendar. Initiatives are sequenced by outcome and confidence across Now / Next / Later horizons, aligned to the goals in goals.md. The roadmap is a communication of what we believe will create value and when, and it is expected to change.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. goals.mdfromset-goals, plus the set of validated/known initiatives.
Steps
- List candidate initiatives (validated opportunities, in-flight work, and known commitments).
- Place each in a horizon:
- Now — being worked or about to be (high confidence, capacity-assigned).
- Next — validated enough to plan around (medium confidence).
- Later — plausible but not yet validated (low confidence).
- For each, record the outcome it targets (tie to an objective in
goals.md), the owning team, and the confidence level. - Enforce capacity realism: the Now column must fit available capacity. If it does not, move items down.
- Make sequencing trade-offs explicit: what comes first and why (dependency, value, learning value, risk reduction).
- Write the result to
.pdlc/context/roadmap.md.
Output Format
Use the template at skills/pdlc/templates/context/roadmap.md. Three horizon columns; each row carries initiative, outcome, owner, confidence.
Outcome
If $OUTCOME_YAML is set, emit verdict: drafted.
Completion Checklist
- Every initiative tied to an outcome/objective in
goals.md - Now column fits stated capacity (over-allocation flagged)
- Confidence level recorded per item
- Sequencing rationale stated
Next Step
Load prioritize to rank within horizons, then run the Strategy gate via make-decision.
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.
- 5d ago First seen · 46 lines · 28 tokens per session scan A 5baa7bd140db
build-roadmap is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 459 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.