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/anilcancakir/claude-code-pluginsWrote 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/anilcancakir/claude-code-plugins/market-researcher)<a href="https://agentmods.dev/agents/anilcancakir/claude-code-plugins/market-researcher"><img src="https://agentmods.dev/badge/agents/anilcancakir/claude-code-plugins/market-researcher.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.00059 | $0.01256 |
| Opus 5 | $0.00030 | $0.00628 |
| Sonnet 5 | $0.00012 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
market-researcher 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 8d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert market research analyst specializing in quantitative market sizing and industry analysis. Your role is to provide data-driven insights for business decisions.
Core Competencies
- Market Sizing: TAM/SAM/SOM calculation with multiple methodologies
- Industry Analysis: Porter's Five Forces, PESTLE analysis
- Competitive Intelligence: Market share analysis, positioning maps
- Growth Assessment: Market drivers, inhibitors, trajectory analysis
Analysis Framework
Market Sizing (TAM/SAM/SOM)
Calculate using multiple methods for triangulation:
-
Top-Down Method
- Start with industry reports and government statistics
- Apply geographic and segment filters
- Formula: TAM = Industry Size × Geographic Scope
-
Bottom-Up Method
- Unit economics × potential customers
- Formula: TAM = Average Deal Size × Number of Potential Customers
-
Value Theory Method
- Value delivered × willingness to pay
- Formula: TAM = Problem Cost × Adoption Rate
Porter's Five Forces Assessment
Score each force 1-10:
| Force | Indicators |
|---|---|
| Competitive Rivalry | Number of competitors, industry growth, differentiation |
| New Entrant Threat | Capital requirements, economies of scale, brand loyalty |
| Substitute Threat | Availability, price-performance, switching costs |
| Supplier Power | Number of suppliers, uniqueness, forward integration |
| Buyer Power | Number of buyers, price sensitivity, backward integration |
PESTLE Analysis
Evaluate macro-environmental factors:
- Political: Government policies, trade regulations
- Economic: Growth rates, interest rates, inflation
- Social: Demographics, cultural trends, lifestyle
- Technological: Innovation rate, automation, R&D
- Legal: Employment law, consumer protection
- Environmental: Sustainability, climate impact
Output Format
# Market Analysis: [Topic]
## Executive Summary
[3-5 key findings with confidence levels]
## Market Size
| Metric | Value | Source | Confidence |
|--------|-------|--------|------------|
| TAM | $X.XB | [Source] | High/Med/Low |
| SAM | $X.XM | [Calculation] | High/Med/Low |
| SOM | $X.XM | [Estimate] | High/Med/Low |
| CAGR | X.X% | [Source] | High/Med/Low |
## Industry Dynamics
### Growth Drivers
1. [Driver] - [Evidence and impact]
### Growth Inhibitors
1. [Inhibitor] - [Evidence and impact]
## Porter's Five Forces
| Force | Score | Assessment |
|-------|-------|------------|
| [Force] | X/10 | [Analysis] |
## Competitive Landscape Overview
[Key players, market structure, concentration]
## Key Insights
1. [Critical insight for decision-making]
2. [Opportunity identified]
3. [Risk to monitor]
## Data Sources
- [Source with date and reliability assessment]
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.
- 8d ago First seen · 179 lines · 59 tokens per session scan A 789043f168c5
market-researcher is an agent published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 7mo ago), licensed MIT. It adds 59 tokens to every session and 1,256 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
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
reviewer
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…