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 commands/buildermethods/design-os/product-roadmapgit clone --depth 1 https://github.com/buildermethods/design-osWhat 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.00000 | $0.00664 |
| Opus 5 | $0.00000 | $0.00332 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
product-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 2d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Roadmap
You are helping the user create or update their product roadmap for Design OS.
Step 1: Check Current State
First, check if /product/product-roadmap.md exists.
If Roadmap Already Exists (Updating)
Read both:
/product/product-overview.md/product/product-roadmap.md
Present the current state and ask what to change:
"Your product roadmap currently has [N] sections:
- [Section 1] — [Description]
- [Section 2] — [Description]
- [Section 3] — [Description]
What would you like to change about the sections?"
Wait for the user's response describing what they want changed. Once you receive their notes, immediately proceed to update product/product-roadmap.md based on their requested changes — do not present a draft for approval.
After updating, inform the user:
"I've updated the product roadmap based on your feedback. Review the changes and let me know if you'd like further adjustments."
Stop here — the remaining steps below are for generating a new roadmap from scratch.
If No Roadmap Exists (Creating New)
Check Prerequisites
Read /product/product-overview.md. If it doesn't exist:
"Before creating a product roadmap, you'll need to define your product vision. Please run /product-vision first."
Stop here if the product overview is missing.
Analyze and Generate
Read the product overview and analyze:
- The core description
- The problems being solved
- The key features listed
Immediately proceed to create /product/product-roadmap.md — do not present a draft for approval. Generate 3-5 sections that represent:
- Navigation items - main areas of the product UI
- Roadmap phases - logical order for building
- Self-contained feature areas - each can be designed and built independently
Use this exact format:
# Product Roadmap
## Sections
### 1. [Section Title]
[One sentence description]
### 2. [Section Title]
[One sentence description]
### 3. [Section Title]
[One sentence description]
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.
- 2d ago First seen · 98 lines · 0 tokens per session scan A 9fc7277f8d09
product-roadmap is a command published in the GitHub repository buildermethods/design-os (1,848 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 664 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.