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/captainme-ai/lead-dev-os/plan-roadmapnpx 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 for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.
[](https://agentmods.dev/skills/captainme-ai/lead-dev-os/plan-roadmap)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 | $0.00015 | $0.00438 |
| Opus 5 | $0.00008 | $0.00219 |
| Sonnet 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 3d 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.
- 3d 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 13d ago), licensed MIT. It adds 15 tokens to every session and 438 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-08-31.
Other skills, from other repositories
develop
Run /develop to build a feature, UI or backend, from an approved design, a page, component, API, service, or data slice. If something load bearing is undecided and no spec records it, it stops and routes you to /architect; otherwise it reads the spec plus AGENTS.md, builds, and advances the scope.
sync
Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns. Never a whole section, never…
test
Run /test to write a test suite for code you just built or changed, after implementing a feature, route, or fix. Targets uncommitted changes automatically, reads test preferences.json for your framework (asks and saves it if absent), and picks the right strategy per file: happy path, edge cases, error states…
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
debug
Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.
check
Confirm a change before merge. /check verify drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). /check review runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never…