Borrowing it
Nothing to install: this file belongs to Ovid/paad. 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/Ovid/paad/main/.claude/skills/roadmap/SKILL.mdgit clone --depth 1 https://github.com/Ovid/paadWrote 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/ovid/paad/roadmap)<a href="https://agentmods.dev/skills/ovid/paad/roadmap"><img src="https://agentmods.dev/badge/skills/ovid/paad/roadmap/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/ovid/paad/roadmap"><img src="https://agentmods.dev/badge/skills/ovid/paad/roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 113 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Prompt Injection · line 309 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 651 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Excessive Agency · line 182 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00027 | $0.15566 |
| Opus 5.5 | $0.00011 | $0.06226 |
| Sonnet 5.5 | $0.00005 | $0.03113 |
| Haiku 4.5 | $0.00003 | $0.01557 |
Grade A, and why
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 2mo 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 — 963 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start
Announce: "Checking for in-progress runs and roadmap layout…"
Read @CLAUDE.md.
Per-Phase Checklist File
One checklist per /roadmap run, created right after step 2a (branch checkout succeeded), updated at the end of every subsequent step. The checklist lives at docs/roadmap/plans/YYYY-MM-DD-<topic>-checklist.md — alongside the design and plan files for the same run.
Filename
YYYY-MM-DD-<phase-slug>-checklist.md, where <phase-slug> is the phase filename slug (defined immediately below), and YYYY-MM-DD is the day step 0 → step 1 fires (start date) — so the design / plan / checklist for one run sit alphabetically adjacent in plans/.
Phase filename slug
A single rule, used by checklist filenames here and referenced from §2a and §Appendix:
- Take the phase title text (everything after the
Phase N:orPhase Na:prefix in the roadmap heading). - Lowercase.
- Drop apostrophes (
',',') without inserting a separator (soEditor'sbecomeseditors, noteditor-s). - Replace any run of non-
[a-z0-9]characters with a single hyphen. - Strip leading and trailing hyphens.
- If the result is empty (e.g. the title was only Unicode/CJK characters that collapsed to nothing), fall back to
phase-Nusing the phase number — including any sub-letter — from the heading.Phase 3a: 漢字→phase-3a.
Examples:
| Phase heading | Phase filename slug |
|---|---|
Phase 1: Backend Foundation |
backend-foundation |
Phase 3a: Movie Data Cleaning |
movie-data-cleaning |
Phase 7: User Authentication implementation |
user-authentication-implementation |
Phase 9: Editor's Polish |
editors-polish |
Phase 12: Implementation |
implementation |
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.
- 2mo ago First seen · 963 lines · 27 tokens per session scan A a376b8c3e0f2
roadmap is a skill published in the GitHub repository Ovid/paad (150 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 15,566 once invoked, about $0.0001 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.
roadmap compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| roadmapOvid/paad | Skill | 150 | yesterday | MIT | A | 27 | Claude Code |
| nopuawuji-labs/nopua | Skill | 1.4k | 1mo ago | MIT | A | 90 | Claude Code |
| nopua-litewuji-labs/nopua | Skill | 1.4k | 1mo ago | MIT | A | 46 | Claude Code |
| compose-expertaldefy/compose-skill | Skill | 599 | yesterday | none | A | 185 | Claude Code, Codex |
| swiftui-macoskageroumado/swiftui-macos-skill | Skill | 13 | 20d ago | MIT | A | 150 | Claude Code |
| wgmagent-frontier/wgm | Skill | 3 | 3d ago | MIT | A | 155 | Claude Code, Codex |
| ruggedagent-frontier/wgm | Skill | 3 | 3d ago | MIT | A | 182 | Claude Code, Codex |