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 heyparsadev/claude-venture-plugin --skill market-researchgit clone --depth 1 https://github.com/heyparsadev/claude-venture-pluginWrote 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/heyparsadev/claude-venture-plugin/market-research)<a href="https://agentmods.dev/skills/heyparsadev/claude-venture-plugin/market-research"><img src="https://agentmods.dev/badge/skills/heyparsadev/claude-venture-plugin/market-research/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/heyparsadev/claude-venture-plugin/market-research"><img src="https://agentmods.dev/badge/skills/heyparsadev/claude-venture-plugin/market-research.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.00117 | $0.01206 |
| Opus 5 | $0.00059 | $0.00603 |
| Sonnet 5 | $0.00023 | $0.00241 |
| Haiku 4.5 | $0.00012 | $0.00121 |
Grade A, and why
market-research 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 11d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Research — Sizing, Trends & Segments
Produce decision-grade market research: how big is the opportunity, how is it changing, which segment to enter first. Numbers must be traceable (cited) and honest (confidence-rated) — a wrong TAM quietly poisons every later module.
Shared conventions (venture suite)
- Workspace: locate
ventures/in the current working directory (ask once and create if missing). All outputs go toventures/<slug>/<NN-module>/. - Templates are read-only. Files under a skill's
references/live inside the installed plugin and are shared by every venture. Never write to them. "Fill template X" always means: copy it intoventures/<slug>/<NN-module>/under a dated name and fill the copy. - Read
VENTURE.mdfirst. When done: update its Status table and append key findings to "Key facts & numbers" (format:- [module, YYYY-MM-DD] finding (source, confidence)). - Language: converse in the user's language. Write formal deliverables (reports, canvases, battlecards) in the
report_languageset in VENTURE.md. Persian reports keep standard English business terms as-is (TAM, SAM, SOM, CAC, LTV, GTM, churn, retention...). - Research integrity: cite every external claim (source + date). Mark every estimate with confidence (high/med/low). Never fabricate numbers — write "no data found" instead.
- Chain: end by updating VENTURE.md and suggesting the logical next module.
Workflow
1. Scope (with the user, briefly)
From VENTURE.md + one quick exchange, pin down:
- Market definition — the job being done, not the product category ("appointment no-show reduction for clinics", not "SaaS").
- Geography — local market vs global changes sources and method entirely.
- Mode —
quick(~10 min scan: top-line size, 3–5 trends, segment list) ordeep(full report). Default: quick forideastage, deep otherwise. State which mode you're running.
2. Research
Consult references/data-sources.md for where to look and references/sizing-guide.md for method. Core rules:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 63 lines · 117 tokens per session scan A b63437f51d63
market-research is a skill published in the GitHub repository heyparsadev/claude-venture-plugin (6 stars, last pushed 29d ago), licensed MIT. It adds 117 tokens to every session and 1,206 once invoked, about $0.0006 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
competitor-research-playbook
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
your-tam-is-fake
Go-to-market strategist that researches before it reacts and refuses to flatter. Sizes the market bottom-up, names the ICP and the wedge, prices the motion, finds the load-bearing assumption, and gives a ranked verdict with kill criteria. Invoke with /your-tam-is-fake; stays on until "stop tam mode".
demand
A research workflow for checking whether a product idea or customer need is real and worth pursuing. It gathers evidence from industry data, investment activity, online communities, app reviews, searches, and social discussion.
foundry-lens
Runs a multi-pass research method that deliberately catches its own blind spots — a shallow first pass, a forced structural self-diagnosis, then corrected and inverted passes. Use when mapping a product's full feature set, tearing down a competitor, doing exhaustive documentation research, or any time a first answer…