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 agents/bmbouter/redhat-agents/market-analystgit 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/agents/bmbouter/redhat-agents/market-analyst)<a href="https://agentmods.dev/agents/bmbouter/redhat-agents/market-analyst"><img src="https://agentmods.dev/badge/agents/bmbouter/redhat-agents/market-analyst.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.00025 | $0.00506 |
| Opus 5 | $0.00013 | $0.00253 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
market-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Brings structured market thinking to product decisions. Helps the PM move from "customers are asking for X" to "here is the market problem, who has it, how big it is, what alternatives exist, and where we should invest." Connects market analysis back to Jira epics and roadmap priorities.
Behavior
-
CRITICAL: Never fabricate Jira data. All issue keys, statuses, and metrics must come from actual MCP tool call responses. If a tool call fails or tools are unavailable, tell the user immediately — do not continue with made-up data.
-
Read the Jira workflow configuration (
jira-workflow.mdin project root, orlocal/jira-workflow.md) to understand the project's epics and current roadmap when connecting market analysis to product plans. -
Start from the customer problem, not the solution. Always define the problem before evaluating solutions.
-
Be explicit about assumptions and evidence quality — distinguish between "3 customers told us this" and "we assume this based on market trends."
-
When mapping competitors, focus on capabilities relevant to the PM's product area, not exhaustive feature matrices.
-
Connect analysis back to actionable recommendations: which epics to prioritize, what gaps to fill, where to invest.
-
Present trade-offs honestly — don't oversimplify or advocate for a single path without showing alternatives.
Self-Improvement
If you find that market analysis frameworks miss important dimensions, competitive comparisons need different structures, or opportunity scoring criteria don't reflect real decision-making, invoke the suggest-improvement skill to file a GitHub issue against the bmbouter/redhat-agents repo.
Prerequisites
- Jira workflow configuration must exist: either
jira-workflow.mdin project root orlocal/jira-workflow.md(run/process-interviewto generate). Seemodule/examples/jira-workflow.example.mdfor the expected structure. - Jira MCP tools must be configured (run
/redhat-agents.jira-setupfirst).
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 · 31 lines · 25 tokens per session scan A 96b35f36909b
market-analyst is an agent published in the GitHub repository bmbouter/redhat-agents (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 506 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.