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.
git clone --depth 1 https://github.com/ericvtheg/solo-founder-toolkitWrote 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/commands/ericvtheg/solo-founder-toolkit/solo-validate-idea)<a href="https://agentmods.dev/commands/ericvtheg/solo-founder-toolkit/solo-validate-idea"><img src="https://agentmods.dev/badge/commands/ericvtheg/solo-founder-toolkit/solo-validate-idea.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.00015 | $0.02030 |
| Opus 5 | $0.00008 | $0.01015 |
| Sonnet 5 | $0.00003 | $0.00406 |
| Haiku 4.5 | $0.00002 | $0.00203 |
Grade A, and why
solo-validate-idea 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 8d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are helping a solo founder validate a product idea or feature. Your goal is to apply the solo-founder-anti-patterns skill to identify risks and calculate a Solo Founder Risk Index (SFRI) score.
Input
The user has provided: {{idea}}
Your Process
1. Load the Anti-Patterns Skill
Invoke the solo-founder-anti-patterns skill to access the validation framework, SFRI rubric, and anti-pattern detection.
2. Ask Clarifying Questions
You MUST ask clarifying questions to reduce ambiguity and gather context. Use AskUserQuestion to collect information needed for proper validation.
Required context areas:
- Problem & Users: What problem does this solve? Who experiences this problem daily?
- Validation evidence: Have you talked to users about this? Are they paying for alternatives?
- Time investment: How many hours do you estimate this will take? What's your runway?
- Revenue impact: Will this drive new sign-ups, reduce churn, or increase conversions?
- Alternatives: What happens if you don't build this? What workarounds exist?
- Technical complexity: Does this require learning new tech or can you use existing patterns?
Example clarifying questions:
- "How many users have explicitly requested this feature?"
- "Are there competitors offering this? If so, what do they charge?"
- "Do you currently have paying users, or is this pre-launch?"
- "What's your current MRR and what's your revenue goal for this feature?"
- "Will this require new infrastructure (databases, services, third-party APIs)?"
Ask 2-4 questions at a time. Don't ask everything at once.
3. Detect Anti-Patterns
Once you have context, identify which anti-patterns apply:
Common anti-patterns to check:
- ✋ 95% Ready Trap: Is this feature creep delaying launch?
- ✋ Competitive Feature Parity: Building this just because a competitor has it?
- ✋ Free User Validation: Relying on waitlist sign-ups instead of payment evidence?
- ✋ Infrastructure Sophistication Trap: Over-engineering the technical solution?
- ✋ Indie Hacker Bubble: Building for other indie hackers instead of real businesses?
- ✋ Maintenance Tax: Will this require ongoing manual support?
- ✋ Dopamine Trap: Building because it's fun rather than revenue-driving?
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.
- 8d ago First seen · 238 lines · 15 tokens per session scan A 2f19fc201d49
solo-validate-idea is a command published in the GitHub repository ericvtheg/solo-founder-toolkit (8 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 2,030 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.