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-briefnpx skills add bmbouter/redhat-agents --skill roadmap-briefgit 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-brief)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/roadmap-brief"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/roadmap-brief.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.00023 | $0.00367 |
| Opus 5 | $0.00012 | $0.00183 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
roadmap-brief 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 3d 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
When the PM needs to communicate the roadmap to stakeholders, leadership, or customers.
Instructions
Read local/jira-workflow.md to understand epic conventions.
1. Determine audience and format
Ask the PM:
- Audience: Engineering leadership? Executives? Customers? Cross-team partners?
- Format: Slide deck bullet points? Email? Confluence page? Slack post?
- Focus: Full roadmap? Specific quarter? Specific theme?
- What changed: Any recent shifts to highlight?
2. Query roadmap data
Pull active and upcoming epics with their target dates and progress.
3. Generate the brief
Adapt tone and detail to the audience:
For executives:
- Lead with outcomes and business impact, not technical details
- 3-5 bullet points max per section
- Highlight what shipped, what's coming, what shifted and why
- Include key risks and decisions needed
For engineering leadership:
- Include progress percentages, team assignments, dependency chains
- Flag technical risks and resource constraints
- More detail on what's in progress and what's blocked
For customers:
- Focus on capabilities being delivered, not internal project details
- Use user-oriented language, not Jira ticket summaries
- Frame around problems being solved, not features being built
- Be careful with dates — use quarters or ranges, not specific dates
For cross-team partners:
- Highlight integration points and shared dependencies
- Call out what you need from them and when
- Show your timeline relative to their timeline
Present draft to the PM for tone and accuracy review before sharing.
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.
- 3d ago First seen · 53 lines · 23 tokens per session scan A c8f6b8160015
roadmap-brief is a skill published in the GitHub repository bmbouter/redhat-agents (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 367 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…