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 CaptainMe-AI/lead-dev-os --skill plan-roadmapgit clone --depth 1 https://github.com/CaptainMe-AI/lead-dev-osWrote 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/captainme-ai/lead-dev-os/plan-roadmap)<a href="https://agentmods.dev/skills/captainme-ai/lead-dev-os/plan-roadmap"><img src="https://agentmods.dev/badge/skills/captainme-ai/lead-dev-os/plan-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/captainme-ai/lead-dev-os/plan-roadmap"><img src="https://agentmods.dev/badge/skills/captainme-ai/lead-dev-os/plan-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.00015 | $0.00438 |
| Opus 5.5 | $0.00006 | $0.00175 |
| Sonnet 5.5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
plan-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 1mo 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
Plan Roadmap
Create or update a prioritized product roadmap with phased milestones.
Instructions
You are a strategic product planner. Help the user create a phased roadmap.
Phase 1: Context Gathering
-
Read
agents-context/README.mdfirst — use this index to understand what concepts already exist. Then readagents-context/product/product-mission.mdif it exists. If it doesn't, ask the user to run/lead-dev-os:plan-productfirst or provide a brief product summary. -
Ask the user:
- What features or capabilities are most critical for your first release?
- Are there any hard deadlines or external dependencies? (Launches, integrations, compliance dates)
- What is your team's capacity? (Solo developer, small team, multiple teams)
- Are there features you've already started or completed?
Phase 2: Roadmap Creation
Organize features into phases based on priority, dependencies, and complexity using the template in template.md. For a filled-in example, see examples/saas-project-tracker.md.
Phase 3: Output
Save the document to agents-context/product/product-roadmap.md.
Phase 4: Update README
Read agents-context/README.md. Under the ## Product section, ensure there is an uncommented entry for product-roadmap.md. If the entry is inside an HTML comment block, uncomment it. If no entry exists, add one:
- **[product-roadmap.md](product/product-roadmap.md)** — Prioritized feature roadmap with phased milestones
Phase 5: Summary
Tell the user:
- "Roadmap saved to
agents-context/product/product-roadmap.md" - "Updated
agents-context/README.mdindex" - Suggest picking a feature from Phase 1 and running
/lead-dev-os:step1-write-specto begin speccing it out.
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.
- 1mo ago First seen · 48 lines · 15 tokens per session scan A e2c924d26f95
plan-roadmap is a skill published in the GitHub repository CaptainMe-AI/lead-dev-os (2 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 438 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
engagement-scoping
Resolve the documentation engagement scope from the settings cascade — project identity, source roots, output root, delivery mode, action ceiling, confidentiality default, and the exact file set this run may touch — and freeze it to /00-control/.scope.json. Use when any /dossier: command starts, when the delivery mode…
finding-reconciliation
Merge the independent A/B/C findings tables into one adjudicated ledger in 07-verification/documentation-verification-report.md — normalizing to the finding schema, deduplicating by location and claim, recording per-finding corroboration without downgrading single-pass findings, promoting cross-pass disagreement to…
project-modeling
Build one canonical project model — entities, boundaries, owners, lifecycle state, and end-to-end traces — and record its authoritative names in 00-control/terminology-and-ownership.md (TM-####), then project that single model into every audience view without ever forking it. Use when starting Phase 2, when the…
gap-and-contradiction-register
Maintain 00-control/assumptions-questions-and-contradictions.md — the assumptions and open-questions register (AQ-####) and the contradiction register (CT-####) — classifying each entry as blocking, material but non-blocking, or minor, and routing blocking gaps to owner resolution before drafting proceeds. Use when a…
scoring-and-release-gate
Score a documentation package against the ten-dimension weighted rubric in references/scorecard-rubric.md with a cited justification per dimension, then evaluate the nineteen conditions in references/release-gate-conditions.md and emit a binary release-ready, conditionally-ready, or not-ready verdict with…
initializing-ledger
Use when starting a new product development project that needs traceable evidence and explicit decisions. Creates workspace structure from a project brief.