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 competitive-landscapegit 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/competitive-landscape)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/competitive-landscape"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/competitive-landscape/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/competitive-landscape"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/competitive-landscape.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00569 |
| Opus 5.5 | $0.00010 | $0.00228 |
| Sonnet 5.5 | $0.00005 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
competitive-landscape 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 1mo 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 — 74 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 understand competitive positioning for a feature area, prepare for a strategy discussion, or respond to "why don't we have what X has?"
Instructions
1. Define the scope
Ask the PM:
- Capability area: What specific area are we comparing? (e.g., "container registry performance", "RBAC model", "CDN integration")
- Competitors: Who should we compare against? Or should we identify them?
- Purpose: Strategic planning? Customer question? RFP response? Feature prioritization?
2. Gather information
For each competitor, research:
- What they offer in this capability area
- How it works (architecture, approach, user experience)
- Strengths: What they do well
- Weaknesses: What they don't do well or don't support
- Pricing/availability: Open source? Paid? Enterprise-only?
- Market perception: How are they positioned?
Also check our own product:
- Query Jira for existing or planned epics in this area
- Review current capabilities
3. Build the comparison
## Competitive Landscape: [Capability Area]
### Our Position
- **Current state**: [What we offer today]
- **Planned**: [Relevant epics on the roadmap]
- **Strengths**: [Where we're ahead]
- **Gaps**: [Where we're behind]
### Competitor Comparison
| Capability | Us | Competitor A | Competitor B | Competitor C |
|------------|-----|-------------|-------------|-------------|
| [Capability 1] | ✅/⚠️/❌ | ... | ... | ... |
| [Capability 2] | ... | ... | ... | ... |
### Detailed Analysis
#### [Competitor A]
- **Approach**: [How they solve it]
- **Strengths**: [What they do well]
- **Weaknesses**: [What they don't do well]
- **Key differentiator**: [What makes them unique]
#### [Competitor B]
...
### Strategic Implications
- **Where we lead**: [Capabilities where we have an advantage]
- **Where we trail**: [Gaps that matter to customers]
- **Where it doesn't matter**: [Differences that aren't meaningful to our segment]
### Recommendations
1. [Invest in X because...]
2. [Don't pursue Y because...]
3. [Monitor Z because...]
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.
- 1mo ago First seen · 74 lines · 24 tokens per session scan A 83145cde091e
competitive-landscape is a skill published in the GitHub repository bmbouter/redhat-agents (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 569 once invoked, about $0.0001 per session on Opus 5.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
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…