Borrowing it
Nothing to install: this file belongs to frostney/pascal-mcp-sdk. 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/frostney/pascal-mcp-sdk/main/.agents/skills/roadmap-review/SKILL.mdgit clone --depth 1 https://github.com/frostney/pascal-mcp-sdkWrote 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/frostney/pascal-mcp-sdk/roadmap-review)<a href="https://agentmods.dev/skills/frostney/pascal-mcp-sdk/roadmap-review"><img src="https://agentmods.dev/badge/skills/frostney/pascal-mcp-sdk/roadmap-review/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/frostney/pascal-mcp-sdk/roadmap-review"><img src="https://agentmods.dev/badge/skills/frostney/pascal-mcp-sdk/roadmap-review.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.00043 | $0.00654 |
| Opus 5.5 | $0.00017 | $0.00262 |
| Sonnet 5.5 | $0.00009 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
roadmap-review 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.
This is a copy
100% identical to roadmap-review — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap review
Produce a source-verified roadmap and throughput-anchored release plan. Analysis is the deliverable; forge changes are optional and confirmation-gated.
Evidence contract
- Pull current issues, releases, milestones, merged PR history, and project direction documents this run. Record missing sources and lower confidence rather than filling gaps from memory.
- Measure 90-day merged-PR throughput and issue-created-to-PR-merged lead time. Use PR-opened-to-merged only as a flagged fallback. Exclude closed triage with no implementation.
- When a domain metric exists, measure its slope from spaced historical CI artifacts. Allocation by label or area describes past effort, not capacity.
- Before proposing or characterizing work, classify it against current code, tests, or primary specifications as Done, Partial, or Absent with evidence. Propose only Partial or Absent work.
Use a small bounded subagent fan-out only for genuinely independent, sizeable evidence areas; otherwise work directly. Synthesize before planning.
Workflow
- Ground the review in the evidence contract and reconcile forge counts.
- Assess release cadence, merged-but-unreleased work, milestone-versus-commit drift, vision, scope, and non-goals.
- Apply measured rates to the counted backlog, with basis and confidence. Never pad the timeline. When evidence cannot support calendar dates, report ranges and dependencies without a dated Gantt or placeholder dates.
- Verify every candidate against source and remove work already delivered.
- Plan themed releases across independent tracks, marking dependencies and the longest pole. Surface genuine human decisions with a recommendation.
- Stop for those decisions and present:
- current state, drift, and release-cadence recommendation;
- measured velocity and confidence;
- versioned, sized tracks;
- throughput-anchored timeline with a Mermaid Gantt when available;
- open decisions.
- Offer a date-stamped
ROADMAP-YYMMDD.md; do not write it without the user's request. - Create or modify milestones, issues, due dates, or labels only after explicit
confirmation of the finalized plan. Create each issue through
/create-issueand report exactly what changed. - After the confirmed milestone and its tracked scope exist, offer
/milestone-rush <milestone>as an explicit next action. Never start the rush automatically; selecting it grants that skill's scoped implementation and merge authority.
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 · 65 lines · 43 tokens per session scan A c65ce0e8631e
roadmap-review is a skill published in the GitHub repository frostney/pascal-mcp-sdk (2 stars, last pushed 4d ago), licensed MIT. It adds 43 tokens to every session and 654 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to roadmap-review, differing in 27 lines, and is treated as a copy.
Other skills, from other repositories
workspace-builder
Build ServiceNow App Engine Studio applications — sysscope creation, scoped tables, sysawworkspace with lists/forms, the sysux record chain behind UI Builder workspaces, data brokers, and application export readiness checks. Never create a UI Builder page by inserting a sysuxpage row.
change-management
Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.
problem-management
Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.
vendor-management
Manage ServiceNow vendors and contracts — corecompany vendor records, astcontract with renewal alerts, astcontractsla performance tracking, vendorriskassessment scoring, and vendor scorecards.
virtual-agent
Build ServiceNow Virtual Agent — syscstopic conversations, topic blocks (text/prompt/script/decision/handoff), NLU utterances and custom entities, quick replies, and KB/incident integration scripts.