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/bmbouter/redhat-agents/roadmap-reviewnpx skills add bmbouter/redhat-agents --skill roadmap-reviewgit clone --depth 1 https://github.com/bmbouter/redhat-agentsWrote 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/bmbouter/redhat-agents/roadmap-review)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/roadmap-review"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/roadmap-review.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.00033 | $0.00528 |
| Opus 5 | $0.00016 | $0.00264 |
| Sonnet 5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
roadmap-review 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 4d 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
When to Use
During planning cycles, before stakeholder reviews, or when the PM suspects the roadmap is drifting.
Instructions
Read local/jira-workflow.md to understand epic conventions and target date custom fields.
1. Query all active epics
project = <PROJECT> AND issuetype = Epic AND status != Closed ORDER BY cf[<target_start>] ASC
2. Analyze each epic
For each epic, gather:
- Target dates: start and end (from custom fields)
- Sub-issue progress: closed / total, status breakdown
- Priority and assignment
- Description completeness: Does it have goals, requirements, acceptance criteria?
3. Check for problems
- No target dates: Epics without start/end dates — invisible on the roadmap
- Overcommitment: Multiple high-priority epics with overlapping timelines and shared assignees
- Timeline conflicts: Epic A depends on Epic B, but A's start date is before B's end date
- Stalled epics: Target end date approaching but sub-issue progress is low
- Scope drift: Epics where sub-issue count has grown significantly since target dates were set
- Orphaned work: Active sub-issues whose parent epic is closed or has no dates
4. Present findings
## Roadmap Health Review — <date>
### Active Epics: X total
### Healthy (Y)
| Epic | Progress | Target | Status |
|------|----------|--------|--------|
| ... | ... | ... | On track |
### At Risk (Z)
| Epic | Progress | Target | Issue |
|------|----------|--------|-------|
| EPIC-123 | 20% | Ends Apr 25 | Only 9 days left, 80% remaining |
| EPIC-456 | 60% | Ends May 1 | Blocked by EPIC-789 which ends May 15 |
### Missing Dates (N)
- EPIC-012 — "Title" — no target dates set
### Overcommitment
- @alice is lead on 3 overlapping epics (EPIC-A, EPIC-B, EPIC-C)
### Recommendations
1. [Specific, actionable recommendation]
2. [...]
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.
- 4d ago First seen · 65 lines · 33 tokens per session scan A dde69269eb66
roadmap-review is a skill published in the GitHub repository bmbouter/redhat-agents (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 528 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-31.
Other skills, from other repositories
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
glab-issue
Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…
sales-ops
Set up and run Airtable-based sales operations and CRM workflows — pipeline management, account and renewal management, deal desk, RFP / tender pipelines, partner CRMs, sales forecasting, vertical CRMs (real estate, mortgage, brokerage, capital markets, public works, nonprofit), and AI-native lean stacks…
jira
Search and manage Jira issues using JQL queries, create/update tickets, and manage workflows. Use when asked to find Jira tickets, check the backlog, manage sprints, track bugs, or work with Atlassian project management.
github
Use this skill when Enoch needs to coordinate work with GitHub: branches, pull requests, issues, reviews, comments, checks, and merges.