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 skills add bmbouter/redhat-agents --skill opportunity-assessmentgit 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/opportunity-assessment)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/opportunity-assessment"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/opportunity-assessment.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.1 | $0.00025 | $0.00698 |
| Opus 5 | $0.00013 | $0.00349 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
opportunity-assessment 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 7d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
When the PM is deciding whether to invest in a feature area, comparing multiple potential initiatives, or building a business case for a new epic.
Instructions
Read local/jira-workflow.md to understand epic conventions and current roadmap structure.
1. Define the opportunity
Ask the PM:
- What is being proposed? (feature, capability, product direction)
- Who is asking for it? (customers, leadership, competitive pressure, internal need)
- What's the hypothesis? (if we build X, then Y will happen)
2. Evaluate across dimensions
Customer demand:
- Search Jira for related issues — how many, from how many reporters, over what time period?
- Are customers asking for this directly, or would it solve problems they're reporting?
- Is demand growing, stable, or one-time?
Competitive positioning:
- Do competitors offer this? Is it a differentiator or table stakes?
- Would building this close a gap or create a lead?
Strategic alignment:
- Does this support stated product/company goals?
- Does it align with where the market is heading?
- Does it strengthen our core or distract from it?
Effort and feasibility:
- If related epics or sub-issues exist, what's the estimated scope?
- Are there technical prerequisites or dependencies?
- Does the team have the expertise?
Risk:
- What happens if we build it and it doesn't get adopted?
- What happens if we don't build it?
- Are there compliance, security, or operational risks?
3. Score and present
## Opportunity Assessment: [Opportunity Name]
### Summary
[One paragraph: what it is, why it's being considered, and the recommendation]
### Scorecard
| Dimension | Score (1-5) | Evidence |
|-----------|-------------|----------|
| Customer demand | X | Y issues from Z reporters |
| Competitive necessity | X | [Gap/lead/parity] |
| Strategic alignment | X | [Supports/neutral/conflicts with goals] |
| Feasibility | X | [Estimated scope, prerequisites] |
| Risk | X | [Low/medium/high, key risks] |
| **Overall** | **X** | |
### Evidence Detail
#### Customer Demand
[Jira data, customer quotes, support trends]
#### Competitive Context
[Where competitors stand, market expectations]
#### Strategic Fit
[Connection to product strategy and company goals]
#### Feasibility
[Scope estimate, dependencies, team readiness]
#### Risks
[What could go wrong, mitigation options]
### Recommendation
[Build / Don't build / Investigate further / Defer]
- **If build**: Suggested priority, timeline, and first steps
- **If not**: Why, and what to tell requestors
### Comparison (if evaluating multiple opportunities)
| Opportunity | Demand | Competitive | Strategic | Feasibility | Risk | Overall |
|-------------|--------|-------------|-----------|-------------|------|---------|
| [A] | ... | ... | ... | ... | ... | ... |
| [B] | ... | ... | ... | ... | ... | ... |
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.
- 7d ago First seen · 95 lines · 25 tokens per session scan A cdfb54d1055f
opportunity-assessment is a skill published in the GitHub repository bmbouter/redhat-agents (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 698 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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…