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 skills/zai-org/synapse/market-researchnpx skills add zai-org/Synapse --skill market-researchgit clone --depth 1 https://github.com/zai-org/SynapseWrote 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/zai-org/synapse/market-research)<a href="https://agentmods.dev/skills/zai-org/synapse/market-research"><img src="https://agentmods.dev/badge/skills/zai-org/synapse/market-research.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.00089 | $0.01522 |
| Opus 5 | $0.00044 | $0.00761 |
| Sonnet 5 | $0.00018 | $0.00304 |
| Haiku 4.5 | $0.00009 | $0.00152 |
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 5d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Use this skill when the user needs market evidence, not just opinions. It should activate for market sizing, opportunity validation, competitor landscape work, segment selection, pricing research, whitespace mapping, and expansion decisions.
This skill is especially useful when the user asks "is this market worth entering?", "how big is the real opportunity?", "who else is already winning here?", or "what evidence would reduce risk before we build, launch, or invest more time?"
Quick Reference
Use the smallest relevant file for the task.
| Topic | File |
|---|---|
| Competitor landscape and gap frameworks | competitor-analysis.md |
| Customer validation and pricing methods | validation.md |
| Evidence quality and confidence rubric | evidence-grading.md |
Research Brief
Start every serious engagement with a compact brief like this:
MARKET RESEARCH BRIEF
Decision:
Target customer:
Geography:
Category or substitute set:
Time horizon:
Must-answer questions:
Evidence bar:
If the brief is weak, the research will drift. Tight questions produce better markets, better comparisons, and better recommendations.
Research Modes
Pick the lightest mode that still answers the decision well. Depth should follow the decision, not ego.
| Mode | Best For | Minimum Output |
|---|---|---|
| Quick scan | Early idea filtering | Market snapshot, top competitors, 2-3 key risks |
| Decision memo | Founders, operators, or investors making a next-step call | Sizing view, segment map, competitor comparison, recommendation |
| Launch validation | New product, feature, or niche entry | Demand signals, pricing checks, interview findings, no-go risks |
| Expansion study | New geography, segment, or adjacent category | SAM filters, local competitors, channel constraints, rollout logic |
Core Rules
1. Define the Decision Before Research Starts
Always anchor the work to one decision:
- enter or avoid a market
- prioritize one segment over another
- shape positioning and pricing
- validate whether to build, launch, or expand
What ships with it
5 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.
- 5d ago First seen · 174 lines · 89 tokens per session scan A 9cb0edb3c0d1
Market Research is a skill published in the GitHub repository zai-org/Synapse (468 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 1,522 once invoked, about $0.0004 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…