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 shiquda/roadmap-skill --skill roadmap-planning-viewsgit clone --depth 1 https://github.com/shiquda/roadmap-skillWrote 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/shiquda/roadmap-skill/roadmap-planning-views)<a href="https://agentmods.dev/skills/shiquda/roadmap-skill/roadmap-planning-views"><img src="https://agentmods.dev/badge/skills/shiquda/roadmap-skill/roadmap-planning-views/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/shiquda/roadmap-skill/roadmap-planning-views"><img src="https://agentmods.dev/badge/skills/shiquda/roadmap-skill/roadmap-planning-views.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.00053 | $0.00382 |
| Opus 5.5 | $0.00021 | $0.00153 |
| Sonnet 5.5 | $0.00011 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
roadmap-planning-views 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
Roadmap Planning Views
Use this skill when roadmap work shifts from backlog management to graph-based planning.
Scope
This skill handles:
- creating a planning view for a selected subset of tasks
- adding or removing tasks from that view
- arranging node layout and notes for a focused workspace
- creating, updating, or removing dependency edges
- analyzing graph structure to find ready, blocked, root, leaf, or isolated work
Keep the unit of work as a chosen subset of tasks inside a named graph workspace.
Recommended workflow
- Determine which project the graph belongs to.
- Identify the subset of tasks that belong in this planning view.
- Create or reuse a planning view with a clear purpose, such as near-term focus, release slice, or future work exploration.
- Add the chosen tasks, then create or refine edges only where relationships matter.
- Run analysis when the user needs execution order or blocking insight.
- Update node notes or layout only to improve clarity of the planning workspace.
- Use more than one planning view when the user wants separate slices such as near-term work versus future work.
Important framing
Treat a planning view as a focused workspace built from a task subset. It supports dependency reasoning, but it is broader than a dependency analyzer.
Use multiple planning views when the user wants separate graphs for different horizons, themes, or execution slices.
References
- Planning view semantics: references/planning-views.md
- MCP mapping: references/mcp-mapping.md
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 · 42 lines · 53 tokens per session scan A 8015ce0053a0
roadmap-planning-views is a skill published in the GitHub repository shiquda/roadmap-skill (82 stars, last pushed 7mo ago), licensed MIT. It adds 53 tokens to every session and 382 once invoked, about $0.0002 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-30.
Other skills, from other repositories
kaneo-cli
Work with Kaneo tasks, projects, comments and time tracking through the kaneo CLI. Use when the user asks to list, create, update, assign or close Kaneo tasks, see what is assigned to them, comment, log time, or script against a Kaneo workspace on Kaneo Cloud or a self-hosted instance.
jjj
Use when working in Jujutsu repositories for problem tracking, solution management, and code review — implements Popperian epistemology (problems → solutions → critiques) directly in version control.
pm-init
Skill "pm-init" from wei63w/pm-manager, covering user input, outline, 1. scaffold, 2. lifecycle and type and 3. detect spec kit (required).
pm-arch
Skill "pm-arch" from wei63w/pm-manager, covering user input, outline, done when and shared workflow (all /pm- commands).
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
pm-done
Skill "pm-done" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).