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 tuliosousapro/SaaS-blueprint --skill idea-validatorgit clone --depth 1 https://github.com/tuliosousapro/SaaS-blueprintWrote 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/tuliosousapro/saas-blueprint/idea-validator)<a href="https://agentmods.dev/skills/tuliosousapro/saas-blueprint/idea-validator"><img src="https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/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/tuliosousapro/saas-blueprint/idea-validator"><img src="https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/idea-validator.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.00035 | $0.01156 |
| Opus 5 | $0.00017 | $0.00578 |
| Sonnet 5 | $0.00007 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00116 |
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 9d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Validator Skill
When to Use
- After completing Phase 0 (Idea) before entering Phase 1 (Validation)
- When the user proposes a new idea or pivot
- When deciding between multiple product directions
- As a sanity check before committing resources
Tools Required
| Tool | Purpose |
|---|---|
firecrawl_search |
Validate market signals, demand indicators |
firecrawl_extract |
Pull data from market reports, forums |
Instructions
1. Collect Idea Inputs
Get from the user (or from completed Phase 0 deliverables):
- Problem statement: What pain does this solve?
- Target user: Who has this pain? (be specific: role, company size, industry)
- Proposed solution: How does this solve it? (one sentence)
- Revenue model: How does this make money?
- Differentiator: Why can't they just use {existing solution}?
2. Score on 5 Dimensions
Each dimension scored 1-5. Total score determines recommendation.
A. Problem Severity (1-5)
| Score | Criteria |
|---|---|
| 1 | Nice-to-have. Users tolerate current solutions fine. |
| 2 | Mild annoyance. Users complain but don't switch. |
| 3 | Real pain. Users actively search for alternatives. |
| 4 | Hair-on-fire. Users lose money/time daily without a solution. |
| 5 | Mission-critical. Business cannot function without solving this. |
Validate with:
firecrawl_search: "{problem_statement} pain point frustrated"
firecrawl_search: "site:reddit.com {target_user} struggling with {problem}"
B. Willingness to Pay (1-5)
| Score | Criteria |
|---|---|
| 1 | Users expect free. No existing paid solutions. |
| 2 | Users pay reluctantly. < $10/mo willingness. |
| 3 | Established paid market. $10-50/mo common. |
| 4 | Users budget for this. $50-200/mo normal. |
| 5 | Enterprise budgets. $200+/mo, multi-seat deals. |
Validate with:
firecrawl_search: "{category} pricing SaaS"
firecrawl_search: "{competitor} pricing plans"
C. Market Timing (1-5)
| Score | Criteria |
|---|---|
| 1 | Market is saturated or declining. |
| 2 | Market exists but growth is flat. |
| 3 | Growing market with room for new entrants. |
| 4 | Emerging market with strong tailwinds (AI, regulation, etc.). |
| 5 | Category creation opportunity — no one owns this yet. |
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.
- 9d ago First seen · 129 lines · 35 tokens per session scan A dd896a68c0d4
idea-validator is a skill published in the GitHub repository tuliosousapro/SaaS-blueprint (4 stars, last pushed 8d ago), licensed MIT. It adds 35 tokens to every session and 1,156 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
ship-it-or-fix-it
Oracle-frozen Builder and independent-Judge convergence cycle. Load ONLY when the operator explicitly sets Governance Dial G2 for the task, or explicitly names this skill or an active work unit already running it. Never auto-activate on task class, such as security, auth, or payments. If a task seems to warrant G2 and…
test-verification
Requires behavioral, failure-path, and durable-seam evidence for tests and review. Use when writing tests, reviewing test coverage, assessing behavioral test quality, or accepting high-risk behavior on test evidence.
portable-adaptive-planning
Use for planning, roadmaps, design, architecture, sequencing, or before consequential work when no current FINAL plan plus GO covers it. Fire before changes to data or schemas, credentials or auth, production or releases, repository or source-home boundaries, irreversible work, or materially costly mistakes. Re-enter…
reasoning-doctrine
The working method for every nontrivial task: frame the objective, ground load-bearing facts, converge on a route, execute without drift, and verify before delivery. Use for analysis, planning, implementation, debugging, document work, reviews, and multi-stage tasks.
write-maintainable-code
Evaluate minimum-sufficient implementation routes and enforce the selected route for a fixed, authorized outcome. Use after outcome, scope, authority, and acceptance evidence are fixed. Do not choose outcomes, set acceptance, adjudicate governance, grade finished work, design tests alone, conduct security audits, or…
governed-operator
Full governance constitution for work that touches shared state, requires independent review, spans seats, or involves planning, architecture, code, reviews, dispatches, status reports, or canonical records. Not needed for quick factual questions or trivial one-off answers.