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/bjorn-ingmanson/thefroject-plugins/idea-validatornpx skills add bjorn-ingmanson/thefroject-plugins --skill idea-validatorgit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/idea-validator)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/idea-validator"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/idea-validator.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.1 | $0.00046 | $0.00738 |
| Opus 5 | $0.00023 | $0.00369 |
| Sonnet 5 | $0.00009 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
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 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Validator
Validate whether an idea is worth pursuing before investing time and money. The goal is not to prove the idea is good. The goal is to find reasons it might fail, early enough to pivot or abandon.
Writes
outputs/validation-[idea].md
Step 1: Problem Clarity
Answer these honestly:
- What problem does this solve? One sentence. If you need a paragraph, the problem is not clear.
- Who has this problem? Specific person, not "everyone." What is their job title, daily routine, current frustration?
- How painful is it? (Hair-on-fire / annoying / nice-to-have). Only hair-on-fire problems reliably produce paying customers.
- What do they do today? The current solution (even if it is duct tape and spreadsheets) is your real competitor.
- Why has nobody solved this yet? If the problem is real and big, why does a solution not already exist? (Timing, technology, distribution, regulation, or nobody has tried)
Step 2: Market Size
Estimate quickly:
- TAM (Total Addressable Market) — everyone who could theoretically use this
- SAM (Serviceable Addressable Market) — the segment you can actually reach
- SOM (Serviceable Obtainable Market) — realistic first-year target
Use: number of potential customers x what they would pay annually. If SOM is under $100K, this is a side project, not a business. That is fine, but know it going in.
Step 3: Sell Before You Build
The best validation is someone paying you before the product exists.
Methods (ranked by signal strength):
- Pre-sell — describe the product, ask for payment or commitment. A credit card is the strongest signal.
- Landing page — describe the value, measure email signups. Conversion rate matters more than volume.
- Manual delivery — do the thing by hand for 5-10 people. If they pay, the demand is real.
- Interviews — talk to 10+ potential users. But discount what people say they would do. Watch what they actually do.
- Survey — weakest signal. People say yes to everything in surveys.
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 · 65 lines · 46 tokens per session scan A b6bcbd4101cc
idea-validator is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 738 once invoked, about $0.0002 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-31.
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…
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…
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…
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…