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 shawnpang/startup-founder-skills --skill market-researchgit clone --depth 1 https://github.com/shawnpang/startup-founder-skillsWrote 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/shawnpang/startup-founder-skills/market-research)<a href="https://agentmods.dev/skills/shawnpang/startup-founder-skills/market-research"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/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/shawnpang/startup-founder-skills/market-research"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/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.00029 | $0.01676 |
| Opus 5 | $0.00015 | $0.00838 |
| Sonnet 5 | $0.00006 | $0.00335 |
| Haiku 4.5 | $0.00003 | $0.00168 |
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 13d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- market-research — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Research
When to Use
Activate when a founder needs to size a market opportunity using TAM/SAM/SOM, validate market assumptions for a pitch deck, understand growth trends, evaluate market entry, or prepare for investor conversations about addressable market. Trigger phrases include "how big is our market," "TAM/SAM/SOM," "market size," "market opportunity," "is this market big enough," "market trends," "help me with the market slide," or "validate our market assumptions."
Context Required
- From startup-context: product description, target customer segments, pricing model, geographic scope, business model.
- From the user: the market or segment to analyze, known data points (industry reports, customer counts, pricing benchmarks), geographic and industry constraints, whether this is for internal decision-making or external presentation (investor deck), and any specific hypotheses about market dynamics.
Workflow
- Define market boundaries -- Specify the problem space, customer segments, geography, and constraints. "Project management tools" is a different market than "team collaboration software." Precision determines whether the analysis is useful.
- Top-down estimation -- Start from total industry size using industry reports, public company revenues, and government statistics. Narrow to the relevant segment by applying filters for geography, customer type, and product category.
- Bottom-up estimation -- Build independently from unit economics: (number of potential customers) x (price per customer) x (purchase frequency). Cross-validate against the top-down estimate.
- Scope the SAM -- Identify which portion of TAM is realistically serviceable given current product capabilities, pricing, distribution channels, and geographic reach.
- Estimate the SOM -- Project achievable market share in 1-3 years based on competitive position, go-to-market capacity, and current traction.
- Project growth -- Forecast how TAM, SAM, and SOM evolve over 2-3 years. Identify key growth drivers, technology shifts, regulatory changes, and demographic trends.
- Map assumptions -- Surface every critical assumption underlying each estimate. Rate confidence levels and identify how to validate the most uncertain assumptions.
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.
- 13d ago First seen · 93 lines · 29 tokens per session scan A ebb2d80b6f87
market-research is a skill published in the GitHub repository shawnpang/startup-founder-skills (321 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 1,676 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…