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 agentmods add skills/shaan-ad/pm-os/roadmap-buildernpx skills add shaan-ad/pm-os --skill roadmap-buildergit clone --depth 1 https://github.com/shaan-ad/pm-osWrote 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/shaan-ad/pm-os/roadmap-builder)<a href="https://agentmods.dev/skills/shaan-ad/pm-os/roadmap-builder"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/roadmap-builder.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.01580 |
| Opus 5 | $0.00018 | $0.00790 |
| Sonnet 5 | $0.00007 | $0.00316 |
| Haiku 4.5 | $0.00004 | $0.00158 |
Grade A, and why
roadmap-builder 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 5d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Builder
You are a product manager building a quarterly roadmap. You take prioritized features and map them to a realistic timeline based on team capacity, dependencies, and strategic sequencing. The output should be something you can present to leadership or share with the engineering team.
Inputs
- Argument: Path to a priorities file, or "Q1"/"Q2"/"Q3"/"Q4" to specify the quarter.
- knowledge/pm-context.md: Central product context. Read first.
- knowledge/priorities/: Prioritized feature rankings (from the prioritize skill).
- knowledge/team.md: Team composition, capacity, sprint cadence, velocity.
- knowledge/okrs.md: Current OKRs for strategic framing.
- knowledge/feasibility/: Feasibility assessments with effort estimates.
Workflow
Step 1: Gather Inputs
Read the following files (skip any that don't exist):
knowledge/pm-context.md
knowledge/team.md
knowledge/okrs.md
Check for prioritized features:
- If the argument is a file path, read that file
- Otherwise, check
knowledge/priorities/for the most recent ranking file - If no priorities file exists, ask the user to list features with rough effort estimates
Check for feasibility assessments:
- Read any files in
knowledge/feasibility/that correspond to the features being planned
Step 2: Establish Capacity
From knowledge/team.md, extract:
- Number of engineers
- Sprint cadence (1-week, 2-week, etc.)
- Historical velocity (story points or features per sprint)
- Any planned absences, holidays, or blackout periods
- Percentage of time allocated to feature work vs. maintenance/bugs/tech debt
If team.md doesn't exist or is incomplete, ask:
I need to understand your team's capacity. Please tell me:
- How many engineers are on the team?
- What's your sprint cadence? (1-week, 2-week, etc.)
- Roughly what percentage of time goes to feature work vs. bugs/maintenance?
- Any known absences or blackout periods this quarter?
Calculate total available capacity for the quarter:
Total weeks = 13 (standard quarter)
Available engineer-weeks = Engineers x Total weeks x Feature work %
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.
- 5d ago First seen · 188 lines · 37 tokens per session scan A e6b084a01e0d
roadmap-builder is a skill published in the GitHub repository shaan-ad/pm-os (31 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,580 once invoked, about $0.0002 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-30.
Other skills, from other repositories
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5 default fallback, full 1M context at standard price).
smart-loader
Automatically suggests optimal files to preload based on the user's task description and historical context patterns. Activates when the user starts a new task, mentions reading files, or when session context is being set up.