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 batterfried-philosophy172/Agent-Startup-Skills --skill market-scoutgit clone --depth 1 https://github.com/batterfried-philosophy172/Agent-Startup-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/batterfried-philosophy172/agent-startup-skills/market-scout)<a href="https://agentmods.dev/skills/batterfried-philosophy172/agent-startup-skills/market-scout"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/market-scout/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/batterfried-philosophy172/agent-startup-skills/market-scout"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/market-scout.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.00046 | $0.00453 |
| Opus 5.5 | $0.00018 | $0.00181 |
| Sonnet 5.5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
market-scout 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 1mo 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.
This is a copy
100% identical to market-scout — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Market Scout — Research & Validation Agent
Purpose
Prevent building products nobody wants by conducting structured market research before a single line of code is written.
When to Use
- Before starting any new SaaS project
- When validating a pivot or new feature direction
- When the user says "is this idea worth building?"
Process
Step 1: Problem Extraction
Ask the user ONE question: "What specific problem does this solve, and for whom?" Do not proceed until you have a clear answer.
Step 2: Competitor Landscape
Research and present a table of 3-5 existing solutions:
| Competitor | What They Do | Pricing | Key Weakness |
|---|---|---|---|
| Example Co | Solves X for Y | $29/mo | Poor UX for Z |
Step 3: Unique Value Proposition
Based on competitor weaknesses, articulate what makes THIS product different in one sentence. Format: "Unlike [competitor], we [unique advantage] for [target user]."
Step 4: Target User Persona
Define the primary user:
- Role: (e.g., "Solo freelance designer")
- Pain Point: (e.g., "Spends 3 hours/week on invoicing")
- Budget: (e.g., "Willing to pay $10-20/month to save time")
- Current Solution: (e.g., "Using spreadsheets manually")
Step 5: Risk Assessment
Identify 2-3 key risks:
- Market risk (is there demand?)
- Technical risk (can we build this?)
- Monetization risk (will people pay?)
Output
Produce a market_brief.md file with all sections above.
Exit Criteria
- Problem is clearly defined
- At least 3 competitors are identified
- UVP is articulated
- Target persona is defined
- Risks are listed with mitigations
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.
- 1mo ago First seen · 61 lines · 46 tokens per session scan A b8f58a6f63c2
market-scout is a skill published in the GitHub repository batterfried-philosophy172/Agent-Startup-Skills (2 stars, last pushed 15d ago), licensed MIT. It adds 46 tokens to every session and 453 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to market-scout, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.
import
Import a self-contained NeatContext context bundle shared by another person, or reconcile a newer copy of a context already on this machine, leaving the source bundle unchanged. Use only when the user explicitly invokes this skill or asks to import a NeatContext bundle.
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
pipeline-auto
Use when the user wants a substantial feature taken from idea through implementation in one run with as little interruption as possible ("just build it", "don't keep asking me"), or when controlling such a run and a worker question, quorum responses, the drift budget, a human decision, a review class or a completeness…
turbo-pipeline
Use when the user wants a feature built end to end after answering one round of questions and then being left alone — "turbo", "ask me once, then just build it", "I'll answer up front, don't come back to me", "decide the rest yourself". Not for a run that wants a spec approval and no tests (superb:fast-pipeline), one…