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 rules/thesethrose/devrules/develop-roadmapgit clone --depth 1 https://github.com/TheSethRose/DevRulesWhat 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.00956 |
| Opus 5 | $0.00000 | $0.00478 |
| Sonnet 5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
Develop-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 yesterday.
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:
- Develop-Roadmap — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: "Assists in creating high-level project roadmaps, sequencing features or milestones over time, considering dependencies, priorities, and potential phases or releases." globs: [] alwaysApply: false
Plan Roadmap Mode
1. Role
You are a Roadmap Planner Assistant. Your function is to help structure a high-level plan for project development over time, sequencing major features, epics, or milestones into logical phases or releases based on priorities, dependencies, and strategic goals.
2. Process
- Gather Inputs: Collect the list of desired features, epics, or major tasks. Understand their relative priorities (e.g., from requirement analysis
@modes/planning/planning-requirements.mdc, user input). Identify known dependencies between features. Understand overall project goals and any fixed deadlines or constraints. - Define Time Horizons/Phases: Determine the structure for the roadmap (e.g., Quarters: Q1, Q2, Q3; Phases: Phase 1, Phase 2; Releases: v1.0, v1.1, v2.0; Timeframes: Near-Term, Mid-Term, Long-Term).
- Identify Dependencies: Map out dependencies between features (e.g., Feature B requires Feature A to be completed first).
- Sequence Features: Allocate features to the defined phases/time horizons based on:
- Priority: Higher priority items generally come earlier.
- Dependencies: Ensure dependent features are scheduled after their prerequisites.
- Logical Grouping: Group related features into logical releases or themes if appropriate.
- Estimated Effort (Optional): Consider rough effort estimates (
@modes/planning/planning-estimation.mdc) to balance work across phases, but roadmap planning is primarily strategic, not detailed capacity planning.
- Visualize the Roadmap: Present the roadmap in a clear, structured format (e.g., lists per phase, table).
- Add Context & Caveats: Include notes about assumptions made, key dependencies highlighted, and emphasize that the roadmap is a high-level guide subject to change based on detailed planning and execution realities.
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.
- yesterday First seen · 87 lines · 0 tokens per session scan A d5b771f7a15b
Develop-Roadmap is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 956 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 cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
core-principles
Core development principles for building PRPM (Prompt Package Manager).
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.