Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/friedbotstudio/baseline/main/.claude/skills/roadmap-planner/SKILL.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/roadmap-planner)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/roadmap-planner"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/roadmap-planner/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/friedbotstudio/baseline/roadmap-planner"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/roadmap-planner.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.00294 | $0.03711 |
| Opus 5.5 | $0.00118 | $0.01484 |
| Sonnet 5.5 | $0.00059 | $0.00742 |
| Haiku 4.5 | $0.00029 | $0.00371 |
Grade A, and why
roadmap-planner 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.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
roadmap-planner
Prove an execution roadmap's task order is correct by re-deriving it from the source of truth (the vision + spec), then diffing the derivation against the existing plan.
The core insight: a roadmap is a schedule over a dependency graph. Most planning errors are not "wrong task" — they are producer-after-consumer: a task that produces something (a contract, a schema, an SDK, a service) is scheduled after a task that consumes it. Reading the roadmap top-to- bottom never catches this; only building the actual dependency graph does. So we derive the tasks from use-cases, wire the graph explicitly, and let a deterministic pass find every ordering violation.
You produce two artifacts, never a silent overwrite:
- a freshly-derived, dependency-ordered roadmap (a proposal), and
- a delta report vs the existing roadmap — ordering violations, missing/extra tasks, circular dependencies found + how they were broken, and compaction candidates.
The human reviews the delta and decides what to adopt. The existing roadmap is often hand-crafted with context the spec doesn't capture; the derivation's job is to challenge it, not replace it.
Inputs (parameterize per project)
- Corpus — the vision/spec/requirements docs to derive from. Point it at wherever the project keeps
its source of truth (a
docs/spec/**tree, a product-requirements doc, a genesis/seed file, ADRs). Actors + use-cases usually live in the requirements/product docs; modules/engines/services in the architecture/design docs. If the project has no written spec, derive from the README + issue tracker and flag the thin provenance as a finding. - Existing roadmap — the plan to validate. Default:
project.json → roadmap.path(this baseline's default isdocs/roadmap-execution-plan.md). - Buckets — the delivery lanes, project-defined. Set them in the
tasks.jsontop-levelbucketsarray; they only rank ties in ordering. A single-lane project can use one bucket (e.g.app); a platform/product split might useplatform,product,web,app. There is no fixed lane set.
What ships with it
6 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 · 202 lines · 294 tokens per session scan A fe6265eb0479
roadmap-planner is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 294 tokens to every session and 3,711 once invoked, about $0.0012 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
code-review-with-lsp
Code review with LSP-powered code intelligence. Uses MCP tools (diagnostics, hover, references, definition, symbols) for semantic code understanding, not just text grep.
i18n-check
An internationalization (i18n) check for software that supports multiple languages. It compares translation files with the text and translation keys used by the code.
vue-best-practices
A review checklist for Vue 2 and Vue 3 components, covering component names, prop declarations, TypeScript casts, API styles and complex template expressions.
gdpr-audit
GDPR compliance audit of code, plans, schemas, or IaC. Produces a findings report with article citations, severity, confidence, and fixes; flags evidence gaps. Not a substitute for a DPO/lawyer.
cognitive-walkthrough
Deep-dive usability evaluation of specific user tasks. Simulates novice user cognition step-by-step to identify learnability issues, unclear actions, and points of confusion.
owasp-ai-testing
AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 32 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.