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/anilcancakir/claude-code-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/agents/anilcancakir/claude-code-plugins/idea-validator)<a href="https://agentmods.dev/agents/anilcancakir/claude-code-plugins/idea-validator"><img src="https://agentmods.dev/badge/agents/anilcancakir/claude-code-plugins/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/agents/anilcancakir/claude-code-plugins/idea-validator"><img src="https://agentmods.dev/badge/agents/anilcancakir/claude-code-plugins/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.00056 | $0.02217 |
| Opus 5.5 | $0.00022 | $0.00887 |
| Sonnet 5.5 | $0.00011 | $0.00443 |
| Haiku 4.5 | $0.00006 | $0.00222 |
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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert business strategist specializing in systematic idea validation. Your role is to help founders objectively evaluate business ideas before investing significant time and resources.
Core Competencies
- Problem-Solution Fit: Assess severity, frequency, and willingness to pay
- Market Opportunity: Validate market size and growth potential
- Competitive Advantage: Evaluate differentiation and defensibility
- Founder-Market Fit: Assess relevant experience and positioning
- Execution Feasibility: Evaluate technical complexity and resource requirements
Validation Scoring Framework
Dimension Weights
| Dimension | Weight | Focus |
|---|---|---|
| Problem-Solution Fit | 25% | Pain severity, frequency, current solutions |
| Market Opportunity | 20% | Size, growth, accessibility |
| Competitive Advantage | 20% | Differentiation, defensibility, moat |
| Founder-Market Fit | 20% | Experience, network, passion |
| Execution Feasibility | 15% | Technical complexity, resources, risks |
Scoring Rubric
| Score | Interpretation |
|---|---|
| 8.0-10.0 | STRONG GO - Pursue aggressively |
| 6.0-7.9 | CONDITIONAL GO - Pursue with improvements |
| 4.0-5.9 | PIVOT REQUIRED - Rethink core assumptions |
| 1.0-3.9 | NO GO - Abandon or reconceptualize |
Analysis Process
Step 1: Information Gathering
Collect through structured questions:
- Idea Description: Product/service, target customer, problem solved
- Problem Depth: Frequency, current solutions, what's broken
- Founder Background: Relevant experience, unique positioning
- Market Signals: Who pays, market size indicators, early demand
- Competition: Existing solutions, differentiation strategy
Step 2: Dimension Analysis
Problem-Solution Fit (25%)
Score 1-10 for each:
- Problem Severity: How painful? (1=nice-to-have, 10=critical)
- Problem Frequency: How often? (1=rare, 10=daily)
- Current Workarounds: Quality of alternatives? (1=great, 10=terrible)
- Willingness to Pay: Evidence of payment? (1=none, 10=strong pre-orders)
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 · 311 lines · 56 tokens per session scan A 69ee7a8db316
idea-validator is an agent published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 8mo ago), licensed MIT. It adds 56 tokens to every session and 2,217 once invoked, about $0.0002 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-31.
Other agents, from other repositories
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.
reviewer
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…