Borrowing it
Nothing to install: this file belongs to frostney/GocciaScript. 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/GocciaScript/main/.agents/skills/roadmap-review/SKILL.mdgit clone --depth 1 https://github.com/frostney/GocciaScriptWrote 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/gocciascript/roadmap-review)<a href="https://agentmods.dev/skills/frostney/gocciascript/roadmap-review"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/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/gocciascript/roadmap-review"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/roadmap-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00719 |
| Opus 5.5 | $0.00017 | $0.00288 |
| Sonnet 5.5 | $0.00009 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- roadmap-review — 100% identical, 27 lines differ
How it starts
The opening of the file, as written. The whole thing — 74 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; issue, pull-request, milestone, and release 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.
Delegate independent, sizeable evidence areas to context-isolated subagents by default when the host supports it; work directly on small or coupled areas. Synthesize before planning.
Workflow
- Ground the review in the evidence contract and reconcile issue, pull-request, release, and milestone counts from the Git hosting service.
- Assess release cadence, merged-but-unreleased work, milestone-versus-commit drift, vision, scope, and non-goals.
- Classify every candidate under the evidence contract and drop work already delivered.
- Apply measured rates to the counted remaining 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.
- 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.
- 3d ago Changed 7c47e78c38d8
- 22d ago Changed · +3 lines 04cc10b38e9d
- 26d ago Changed · +3 lines 2caf128422ad
- 29d ago Changed · +3 lines 083f9b443e5a
- 1mo ago First seen · 65 lines · 43 tokens per session scan A c65ce0e8631e
roadmap-review is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 719 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
javascript-expert
Expert-level JavaScript development with modern ES2024+ features, Node.js, npm ecosystem, and best practices. Use when the user mentions ECMAScript, ES2024, Node.js, npm, or web, or when the task involves Modern JavaScript, Node.js Development, Modern Tooling, or Functional Programming.
qcad
Use when editing DXF files with a professional open-source 2D CAD application — CAM output, part libraries, isometric projection. QCAD: open-source 2D CAD with DXF as native format, scriptable via ECMAScript.
git-step-commit
Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…
manage-prd-docs
Automatically manage product requirements across current decisions in docs/PRD.md and docs/prd/, mature future plans under docs/plans/, and active implementation under docs/work/. Use whenever the conversation discusses, clarifies, versions, plans, implements, completes, splits, or migrates a product requirement or…
modernize-ecmascript
A guide for writing or reviewing JavaScript and TypeScript using newer ECMAScript language features. ECMAScript is the standard behind JavaScript, and the guide checks whether the project's tools and target browsers or runtimes can handle each feature.
file-line-audit
Audit oversized source files in a repository. Apply repository .gitignore rules plus extra exclude patterns, filter candidate files with include glob patterns, count physical lines, and output only files at or above the threshold. Use this skill when the user asks to find long files, review file-length distribution…