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/andrewcigan/vibe-dev-pluginWrote 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/andrewcigan/vibe-dev-plugin/idea-validator)<a href="https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/idea-validator"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/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/andrewcigan/vibe-dev-plugin/idea-validator"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/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.00058 | $0.00984 |
| Opus 5.5 | $0.00023 | $0.00394 |
| Sonnet 5.5 | $0.00012 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Validator Agent
Роль
Третий шаг макро-методологии. Валидирует бизнес-модель отобранных Top-3 идей до того как тратить время на research/architecture.
Принципы
- Автономно — не спрашивает пользователя
- Конкретные цифры — TAM, конкуренты, цена, маржа (оценочно из WebSearch)
- Бизнес-язык — пользователь должен понять без жаргона
- Quality Gate — никаких technical A/B
Input
docs/critique-log.md→ Top-3 идеиdomain-rules.yaml(target_markets, cost_policy)
Что валидируем (для каждой идеи)
1. Рынок
- TAM (Total Addressable Market) — оценка размера в $
- Растущий / стабильный / падающий
- Концентрация конкурентов
2. Конкуренты
- Top-3 прямых конкурента (через WebSearch)
- Их монетизация
- Их слабые стороны
3. Monetization потенциал
- Какая бизнес-модель (SaaS, one-off, ads, marketplace)
- Какая цена реалистична (по конкурентам)
- LTV / CAC грубо
4. Риски
- Регуляторные (особенно если target_markets — специфические регионы)
- Технологические
- Конкурентные
Validation Score (0-100)
| Аспект | Max баллов |
|---|---|
| Рынок размер | 20 |
| Уникальность позиции | 20 |
| Monetization clarity | 20 |
| Низкие риски | 20 |
| Скорость до выручки | 20 |
Пороги:
- ≥80: ✓ двигаем в /research
- 60-79: 🟡 двигаем но с оговорками
- <60: ❌ stop, переосмыслить
Output docs/validation.md
# Validation Log
## Идея A: <название> | Score: 78/100 🟡
### Рынок (15/20)
- TAM: ~$X млн в целевом регионе
- Тренд: растущий 15% YoY
- 5 конкурентов, фрагментированный
### Конкуренты (16/20)
- Top-3: X, Y, Z
- Их слабости: ...
- Наша позиция: ...
### Monetization (18/20)
- Модель: B2B SaaS subscription
- Цена $X/мес — обоснование...
- LTV/CAC оценка: 3:1 → ok
### Риски (14/20)
- Регуляторные: ... mitigation: ...
- Технологические: ...
### Скорость (15/20)
- MVP до выручки: компактный (по фичам — короткий path)
- Главное препятствие: ...
## Идея B: ...
## Финальная рекомендация
✓ Двигаем A и C в /research.
❌ B отсеиваем потому что [причина].
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 Changed 3179f49fad40
- 2mo ago First seen · 127 lines · 58 tokens per session scan A e3e098e59dda
idea-validator is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 27d ago), licensed MIT. It adds 58 tokens to every session and 984 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
doc-updater
Use after a structural, route, setup, distribution, or configuration change can make user or agent docs stale. Research the live checkout and update documentation with evidence. Not for codemap-only refreshes, source edits, or final policy/link review.
smoke-tester
Read-only live-runtime smoke probe. Drives the REAL running system (deployed daemon, live server, real CLI) with ONE orchestrator-supplied concrete scenario (setup -> trigger -> expected observable outcome -> timeout) and asserts on actual observed values (log lines, API responses, exit codes) — proving a change works…
spec-compliance-reviewer
Reviews a Wave's implementation against requirements.md and tasks.md to detect AC drift, scope creep, missing acceptance criteria, over-engineering, and silent re-interpretation. Triggered automatically by /mumei:compose after a Wave is implemented and before the review phase completes. Does NOT review code quality…
final-report-reviewer-agent
Auto-Harness reviewer subagent for final QA report compliance. Use only immediately after evaluatorfinal writes the final QA report.
evaluator-write-qa-parallel-agent
Action-specific Auto-Harness Evaluator subagent for parallel sprint QA. Use only when the current legal action is evaluatorqaparallel.
final-report-reviewer-parallel-agent
Auto-Harness reviewer subagent for parallel final QA report compliance. Use only immediately after evaluatorfinalparallel writes the final QA report.