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/stakeholder-briefnpx skills add bmbouter/redhat-agents --skill stakeholder-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/stakeholder-brief)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/stakeholder-brief"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/stakeholder-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.00021 | $0.00537 |
| Opus 5 | $0.00010 | $0.00269 |
| Sonnet 5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
stakeholder-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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
When the PM needs to brief leadership, present at a review, or prepare talking points for a meeting.
Instructions
Read local/jira-workflow.md to understand statuses, epic conventions, and metrics available.
1. Understand the context
Ask the PM:
- Audience: Who is this for? (VP, director, cross-team, skip-level)
- Occasion: Regular review? Escalation? Planning input? Ad-hoc ask?
- Key message: What's the one thing you want them to take away?
- Talking points: Any specific items to include or exclude?
- Format: Bullet points? Slide content? Written summary? Verbal prep notes?
2. Gather data
Query Jira for relevant metrics:
- Epic progress (completion percentages, timelines)
- Recent completions
- Current blockers / risks
- Headcount / capacity utilization (if visible in assignments)
- Trend data (issues opened vs closed over time)
3. Draft the brief
Adapt to audience:
For executives (VP+):
## [Team/Product] Brief — <date>
### Status: [Green / Yellow / Red]
### Key Takeaway
[One sentence — what they need to know]
### Progress Against Goals
| Goal | Status | Notes |
|------|--------|-------|
| [Q goal 1] | On track / At risk / Behind | [Brief context] |
### Risks Requiring Attention
- [Risk 1 — what it is, what you need from them]
### Decisions Needed
- [Decision 1 — options and recommendation]
For engineering leadership:
## [Team/Product] Update — <date>
### Completed Since Last Update
- [Item 1]
### In Progress
| Epic | Progress | ETA | Blockers |
|------|----------|-----|----------|
| ... | ... | ... | ... |
### Risks
- [Risk with specific impact and mitigation]
### Asks
- [What you need from them]
For cross-team:
## [Team/Product] — What You Need to Know
### What We're Working On
- [Items relevant to this audience]
### Dependencies on Your Team
- [Specific ask with timeline]
### Dependencies on Us
- [What they're waiting for and when]
Review with the PM. Adjust tone, detail, and emphasis as requested.
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 · 91 lines · 21 tokens per session scan A 5089995e762c
stakeholder-brief is a skill published in the GitHub repository bmbouter/redhat-agents (5 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 537 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…