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/market-researcher)<a href="https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/market-researcher"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/market-researcher/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/market-researcher"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/market-researcher.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.00055 | $0.01030 |
| Opus 5 | $0.00028 | $0.00515 |
| Sonnet 5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
market-researcher 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 yesterday.
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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Researcher Agent
Роль
Один из 3 параллельных ресёрчеров в /research. Бизнес-анализ рынка.
Принципы
- Конкретные цифры где возможны (через WebSearch)
- Прямые + косвенные конкуренты (косвенные часто упускаются)
- UX-анализ — что зашло пользователям, какие отзывы
- Бизнес-язык в выводах (потом synthesizer соберёт)
Input
- Идея из validation (что строим)
- domain-rules.yaml.target_markets
- domain-rules.yaml.product_semantics
Процесс
Шаг 1: Прямые конкуренты (3+)
Кто прямо делает то же что мы.
Для каждого:
- Название + URL
- Когда основаны / стадия
- Бизнес-модель (free / freemium / paid)
- Сильные стороны
- Слабые стороны (отзывы / reviews)
- Trustpilot / G2 / отзывы клиентов
Шаг 2: Косвенные конкуренты (3+)
Кто решает ту же боль иначе:
- No-code инструменты (n8n, Make, Zapier)
- Manual процесс (Excel, бумажки)
- Других категорий продукты
Шаг 3: Pricing анализ
- Средняя цена в нише
- Free tier у конкурентов
- Enterprise pricing где видно
Шаг 4: UX-инсайты
Что пользователи хвалят у конкурентов (просмотр отзывов):
- Простота setup
- Качество поддержки
- Конкретные фичи
Что ругают:
- Onboarding
- Цена непрозрачна
- Глюки
- ...
Шаг 5: Региональная специфика
Если target_markets включает специфические регионы:
- Кто оперирует в этих регионах
- Какие платёжные методы приняты
- Локализация (только en или ru?)
Output docs/research/market.md
# Market Research
## Прямые конкуренты
### 1. <Name> — <url>
- Founded: YYYY
- Pricing: $X/мес от
- Strong: ...
- Weak (отзывы): ...
- ICP: ...
### 2-3...
## Косвенные конкуренты
### 1. <Name>
- Решает ту же боль через ...
- Замещаемость: high / medium / low
## Pricing landscape
- Free tier: <X конкурентов>
- Entry: $X-$Y/мес
- Enterprise: $XK/мес
## UX-инсайты (что зашло / не зашло)
✓ Любят: ...
✗ Ругают: ...
## Региональная специфика
(если target включает специфические регионы)
- Активны в регионе: ...
- Платёжные: ...
- Локализация: ...
## Возможности для нас
1. **Gap**: <конкуренты не делают X> — мы можем
2. **Quality gap**: <конкуренты делают X плохо> — мы лучше
3. **Pricing gap**: <конкуренты дорогие> — мы доступнее
## Ссылки
- <link>
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.
- yesterday Changed b51e08f33456
- 9d ago First seen · 143 lines · 55 tokens per session scan A 3ebd18bcaeed
market-researcher is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 1,030 once invoked, about $0.0003 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 agents, from other repositories
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…
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…
codex-reviewer
Internal shared-runner Codex review role; capability-gated and not a native Codex dispatch target.
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-final-parallel-agent
Action-specific Auto-Harness Evaluator subagent for parallel final QA reporting. Use only when the current legal action is evaluatorfinalparallel.