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 daliaabbruciati/awesome-claude-skills-by-dalia --skill project-roadmap-managergit clone --depth 1 https://github.com/daliaabbruciati/awesome-claude-skills-by-daliaWrote 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/daliaabbruciati/awesome-claude-skills-by-dalia/project-roadmap-manager)<a href="https://agentmods.dev/skills/daliaabbruciati/awesome-claude-skills-by-dalia/project-roadmap-manager"><img src="https://agentmods.dev/badge/skills/daliaabbruciati/awesome-claude-skills-by-dalia/project-roadmap-manager/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/daliaabbruciati/awesome-claude-skills-by-dalia/project-roadmap-manager"><img src="https://agentmods.dev/badge/skills/daliaabbruciati/awesome-claude-skills-by-dalia/project-roadmap-manager.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.00061 | $0.00548 |
| Opus 5 | $0.00030 | $0.00274 |
| Sonnet 5 | $0.00012 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
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 12d 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 Management
You are responsible for the project's ROADMAP.md file in the project root. It is the single source of truth for what is planned, in progress, and done.
When to create the file
- The user asks for a plan/roadmap for a project or feature.
- Propose the full plan first in chat: phases, tasks, and rough order.
- Do not create ROADMAP.md until the user explicitly approves the plan.
- Once approved, create ROADMAP.md at the project root with the structure below.
Required structure
# <Project Name> — Roadmap
> Status legend: ✅ Done · 🚧 In Progress · ⬜ Planned · ⛔ Blocked
## Progress
- **Phase X of Y** complete
- Overall completion: N%
## Phases
### Phase 1 — <Name>
- **Status:** ✅ | 🚧 | ⬜ | ⛔
- **Goal:** <one sentence>
- [ ] Task 1
- [ ] Task 2
### Phase 2 — <Name> ...
Rules:
- Each phase has: title, a one-line goal, a status badge, and a task checklist.
- Update the Progress summary whenever anything changes.
- Keep tasks concrete and atomic so "done" is clearly verifiable.
Automatic updates (no user prompt needed)
While working on the project, keep the roadmap in sync:
- When a task is finished: tick its checkbox
[x]and update affected statuses. - When an entire phase is finished: flip its badge to ✅ and update the Progress section.
- When current work maps to a phase, mark that phase 🚧 before starting.
- When the plan evolves during development, add new tasks/phases as they are discovered, noting why in a short "Notes / Changes" line per phase.
- Never mark something done that is not functionally complete or verified.
Status transitions
- ⬜ Planned → 🚧 In Progress → ✅ Done
- ⛔ Blocked: use only if something is stuck and needs help; leave a short note on the task.
Final check
When you finish a task or deliver a milestone, state the updated completion percentage and the next phase in your reply.
What ships with it
1 file 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.
- 12d ago First seen · 65 lines · 61 tokens per session scan A 13c70a5a9b10
roadmap is a skill published in the GitHub repository daliaabbruciati/awesome-claude-skills-by-dalia (4 stars, last pushed 18d ago), licensed MIT. It adds 61 tokens to every session and 548 once invoked, about $0.0003 per session on Opus 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.