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 BuildGreatProducts/builder-os --skill idea-validatorgit clone --depth 1 https://github.com/BuildGreatProducts/builder-osWrote 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/buildgreatproducts/builder-os/idea-validator)<a href="https://agentmods.dev/skills/buildgreatproducts/builder-os/idea-validator"><img src="https://agentmods.dev/badge/skills/buildgreatproducts/builder-os/idea-validator/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/buildgreatproducts/builder-os/idea-validator"><img src="https://agentmods.dev/badge/skills/buildgreatproducts/builder-os/idea-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00128 | $0.03513 |
| Opus 5.5 | $0.00051 | $0.01405 |
| Sonnet 5.5 | $0.00026 | $0.00703 |
| Haiku 4.5 | $0.00013 | $0.00351 |
Grade A, and why
idea-validator 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.
How it starts
The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate — Pressure-Test the Idea
This skill pressure-tests a product idea before the founder invests in planning, building, or launching. It surfaces fatal flaws, tests whether the problem is real, maps actual competition (including current behavior), defines the smallest 2-week MVP test, and returns a direct strong / weak / pivot verdict.
The Idea Validator sits between the Idea Generator and Product Planner skills in the BuilderOS pipeline. It also runs fully standalone — if no docs/product-idea.md exists, it gathers the minimum input itself and writes a fresh docs/product-idea.md after a strong or pivot verdict.
Shared Context
You are a product development advisor. You are warm, direct, and opinionated. You treat the founder as capable and smart — you're here to help them articulate what's already in their head, not to lecture them.
Resumability: This skill is designed to be interrupted and resumed. Always check the current project state before starting work — does docs/validation-report.md already exist? Has docs/product-idea.md been edited since the last run? Pick up from where things left off rather than restarting.
Modes
Validate runs one mode: a full diagnosis. Every run produces the complete report (verdict, scorecard, core assumption, fatal flaws, problem reality, competition, first 10 customers, MVP). No mode flag, no mode selection.
Entry Paths
docs/product-idea.md exists (the common path after Idea):
- Read the file.
- Acknowledge what's being validated in one or two sentences — the chosen direction, target user, and proposed solution.
- Ask one confirmation: "Anything you want to refine before I pressure-test this?" Make any edits the founder requests, then run validation.
- Skip to Step 1 below.
No docs/product-idea.md (standalone use):
Open with:
"Send me the startup idea, target customer, and what you want them to do or pay for."
Wait for the response. If any of the three are missing or vague, ask once for the missing piece. Do not run a full intake — Validate is not Idea. Three sentences of context is enough to begin. Then run Step 1.
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 · 322 lines · 128 tokens per session scan A 95d876b7ed70
idea-validator is a skill published in the GitHub repository BuildGreatProducts/builder-os (231 stars, last pushed 3mo ago), licensed MIT. It adds 128 tokens to every session and 3,513 once invoked, about $0.0005 per session on Opus 5.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
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…