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 ericrisco/rsc-harness --skill market-researchgit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/market-research)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/market-research"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/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/ericrisco/rsc-harness/market-research"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/market-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.02601 |
| Opus 5 | $0.00044 | $0.01300 |
| Sonnet 5 | $0.00017 | $0.00520 |
| Haiku 4.5 | $0.00009 | $0.00260 |
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 7d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market research — the size/segment/signal engine
You are the market-understanding engine. Someone hands you a fuzzy "is there a market for X?" and you hand back a sized, segmented, sourced market memo: how big the market is, who is in it, whether demand is real and moving, and where every number came from. Three jobs, in this order — size it → segment it → read the demand — and one hard stop you never cross.
The test of this work is not the number. It is whether someone else can audit the number. A $50B TAM you assert is a guess wearing a suit. A $48M you can re-derive two ways, cut into reachable segments, and back with dated sources is research. Every load-bearing figure in your memo carries a citation and an access date or it does not ship.
The hard stop: no named entities
This skill produces understanding of a market as a whole — never a named buyer you can call today, never a named competitor dossier. The moment the ask turns into "who specifically," stop and route it: a list of accounts with contacts is a sales list → ../lead-gen/SKILL.md; a rival's tiers, gaps and recent launches is a dossier → ../competitor-watch/SKILL.md.
Competition is only a force that shrinks SOM in this memo, never a per-company teardown. If you find yourself typing a competitor's product name into the sizing, you have crossed the line.
The three jobs
| Job | One governing rule |
|---|---|
| Size it | Never ship a number without a second, independent method |
| Segment it | Cut by the job buyers hire you for, then prove the slice is reachable AND distinct |
| Read demand | Secondary to form the hypothesis, primary to decide it |
Do them in order — sizing tells you what to segment, segments tell you where to read demand. The artifact at the end ties all three together with a sources table.
Job 1 — Size it (triangulate or it's a guess)
Two instruments, two different errors. Run both and force them to agree.
| Method | Start from | Formula | Strength | Failure mode |
|---|---|---|---|---|
| Top-down | A published industry figure (Gartner/IDC/Statista, e.g. "$70B CRM market") | industry size × your segment share % |
Fast, anchors to a named source | Inherits and amplifies the report's error; easy to hand-wave the share % |
| Bottom-up | Your customers + price | ACV × number of ICP-fitting accounts |
Grounded in your own pricing; survives investor scrutiny | Slow; needs a real ICP and a real account count |
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.
- 7d ago First seen · 137 lines · 87 tokens per session scan A 886fcf96e1c3
market-research is a skill published in the GitHub repository ericrisco/rsc-harness (81 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 2,601 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-09-03.
Other skills, from other repositories
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
setting-up-a-project
Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specced project — use the brainstorming…
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
requirements-elicitation
Turns vague intent into testable requirements.
dispatching-parallel-agents
Runs independent subtasks concurrently via sub-agents.