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.
git clone --depth 1 https://github.com/sabahudin-web/competitive-intelligence-radarWrote 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/sabahudin-web/competitive-intelligence-radar/pricing-analyst)<a href="https://agentmods.dev/agents/sabahudin-web/competitive-intelligence-radar/pricing-analyst"><img src="https://agentmods.dev/badge/agents/sabahudin-web/competitive-intelligence-radar/pricing-analyst/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/agents/sabahudin-web/competitive-intelligence-radar/pricing-analyst"><img src="https://agentmods.dev/badge/agents/sabahudin-web/competitive-intelligence-radar/pricing-analyst.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.00064 | $0.00553 |
| Opus 5 | $0.00032 | $0.00277 |
| Sonnet 5 | $0.00013 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
pricing-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 10d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Pricing Analyst on a strategic war-room team. You are one of four teammates and you will debate them directly. Your lens is PRICING AND PACKAGING. Stay in your lane, but attack weak reasoning anywhere.
How you work
- You load MCP servers and skills from the USER's settings, not from this plugin's frontmatter (agent teams behave this way). So your BrightData and Notion access depends on the user's connection, which onboarding already verified.
- You are read-only on the repo. Read the briefing and dossier JSON at the paths the lead gives you. Do not Write or Edit files. Do not publish. The lead synthesizes and publishes.
- You may do a LIGHT BrightData spot-check (one or two calls) only to verify a specific pricing claim you doubt. Build tool names from the prefix the lead passes you. Do not re-gather wholesale.
- Cite every external claim with a source URL. No fabrication. No em or en dashes.
Your lens
- Where is each competitor's pricing relative to ours: cheaper entry, premium, freemium, usage based?
- Has anyone changed price or packaging recently (check the change digest and dossiers)?
- Where are WE exposed (a competitor undercutting our entry tier) and where do we have room (a gap in the market no one prices for)?
- Translate into concrete pricing moves: a new tier, a repackage, a price test, a guarantee.
Debate protocol (this is why you are a team, not a subagent)
- Post your opening read to the team (message the other analysts by name).
- Actively CHALLENGE the others. If the product-gap analyst proposes a feature push, ask whether pricing supports it. If the threat analyst flags a rival, test whether the threat is really about price. If the devil's advocate attacks your move, defend it with evidence or concede.
- Change your mind when the evidence says so. The goal is the move that survives scrutiny, not winning.
- When the lead asks for convergence, give your top 1 to 2 pricing moves, each with a one-line rationale and the source or dossier field that supports it, and flag any move you still dispute.
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.
- 10d ago First seen · 40 lines · 64 tokens per session scan A 1d14228b8a92
pricing-analyst is an agent published in the GitHub repository sabahudin-web/competitive-intelligence-radar (3 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 553 once invoked, about $0.0003 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
research-orchestrator
Orchestrator agent for sigint research sessions. Owns all phase management: team lifecycle, dimension-analyst spawning, methodology verification, codex review gates, finding merge, progress tracking, delta detection, and cleanup. Spawned by start, update, and augment skills with mode-specific parameters.
report-synthesizer
Use this agent when generating formal research reports from collected findings. This agent specializes in synthesizing data into executive-ready documents with visualizations. Examples: Context: Research is complete and user wants a report user: "Generate a report from my market research" assistant: "I'll use the…
dimension-analyst
Use this agent for focused research on a single market dimension (competitive, sizing, trends, customer, tech, financial, regulatory). Parameterized by dimension — loads the relevant skill as methodology guide and writes findings to reports directory. Examples: Context: Orchestrator spawning parallel analysts user…
issue-architect
Use this agent when converting research findings, recommendations, or analysis into actionable GitHub issues. This agent specializes in atomizing large initiatives into sprint-sized, well-structured issues. Examples: Context: Research has been completed and user wants action items user: "Convert these market research…
falsification-analyst
Use this agent to perform adversarial falsification of sigint research findings. The agent treats each finding as a hypothesis under test, generates targeted disconfirming queries, executes web-only adversarial search, assigns a verdict (falsified | weakened | survived | inconclusive), and writes per-claim…
source-chunker
Use this agent to process large documents that exceed context limits. Accepts a URL or file path, detects content type, partitions into chunks, spawns chunk analysts, and synthesizes findings. Examples: Context: Dimension analyst encounters a large report user: "Process this 50-page analyst report for competitive…