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 onatm/agent-skills --skill docs-product-roadmapgit clone --depth 1 https://github.com/onatm/agent-skillsWrote 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/onatm/agent-skills/docs-product-roadmap)<a href="https://agentmods.dev/skills/onatm/agent-skills/docs-product-roadmap"><img src="https://agentmods.dev/badge/skills/onatm/agent-skills/docs-product-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/onatm/agent-skills/docs-product-roadmap"><img src="https://agentmods.dev/badge/skills/onatm/agent-skills/docs-product-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.00047 | $0.01321 |
| Opus 5 | $0.00023 | $0.00660 |
| Sonnet 5 | $0.00009 | $0.00264 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
docs-product-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 9d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Product Roadmap
Create living product roadmaps that connect strategy to measurable customer and business outcomes. Communicate priorities and uncertainty without turning the roadmap into a feature inventory, delivery backlog, or set of unsupported date commitments.
Resource Map
- Use
assets/doc-starters/product-roadmap-doc.mdwhen creating or substantially rewriting a product roadmap. - Read
references/product-roadmap-example.mdwhen you need a worked example of outcome-led confidence horizons.
When to Use
- Product strategy must be translated into prioritized outcomes or themes
- A new roadmap needs Now/Next/Later horizons, phases, or genuine time windows
- An existing roadmap needs review after new evidence, strategy, capacity, or dependencies emerge
- Stakeholders need a clear explanation of what is prioritized, why, and with what confidence
Do Not Use
- Requirements for one initiative that belong in
docs-product-requirements - Accepted behavior for one user-visible capability that belongs in
docs-feature-design - APIs, schema, runtime behavior, or implementation design that belongs in
docs-components-design - System topology that belongs in
docs-architecture - Sprint plans, granular task lists, or issue creation that belongs in delivery planning or
linear-task-planning
Workflow
- Identify the roadmap decision and audience.
- Clarify the product or portfolio, planning horizon, intended audience, and decision the roadmap must support
- Find existing vision, strategy, objectives, PRDs, research, analytics, technical constraints, commitments, and roadmap conventions
- Reuse the repository's roadmap location and format; otherwise default to
docs/product/ROADMAP.md - Create audience-specific views only when one view cannot communicate the right level of certainty and detail
- Establish strategy and source inputs.
- State the product direction, target users, strategic objectives, and measurable outcomes before considering initiatives
- Separate evidence, assumptions, decisions, commitments, and unknowns
- Attribute material evidence and note its date, segment, and limitations
- Never invent strategy, capacity, owners, estimates, deadlines, research, or dependencies
- If strategy or outcomes are missing, stop and resolve them or produce a gap plan rather than arranging an ungrounded feature list
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.
- 9d ago First seen · 111 lines · 47 tokens per session scan A 7bf9cbeba65a
docs-product-roadmap is a skill published in the GitHub repository onatm/agent-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,321 once invoked, about $0.0002 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
loom-usage
Meta-orchestration skill for Claude driving loom itself.
curate-collection
Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use…
design-on-call-rotation
Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or…
design-training-program
Design a GxP training programme covering training needs analysis by role, curriculum design (regulatory awareness, system-specific, data integrity), competency assessment criteria, training record retention, and retraining triggers for SOP revisions and incidents. Use when a new validated system requires user training…
conduct-retrospective
Conduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant…
create-work-breakdown-structure
Create a Work Breakdown Structure (WBS) and WBS Dictionary from project charter deliverables. Covers hierarchical decomposition, WBS coding, effort estimation, dependency identification, and critical path candidates. Use after a project charter is approved, when planning a classic or waterfall project with defined…