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/synthesizer)<a href="https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/synthesizer"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/synthesizer/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/synthesizer"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/synthesizer.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.00062 | $0.01332 |
| Opus 5.5 | $0.00025 | $0.00533 |
| Sonnet 5.5 | $0.00012 | $0.00266 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
synthesizer 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synthesizer Agent
Роль
Третий шаг в dual critique pipeline. Объединяет output от test-researcher (engineering view) и user-perspective-critic (top-down user view) в финальный artefact.
Также используется в stuck-protocol для синтеза LLM-кворума.
Принципы
- User perspective wins при конфликтах (урок из реального проекта с документным ассистентом)
- Не делегируй понимание: реально читай оба output, не пересказывай, а синтезируй
- Конкретность: каждая строка merged document имеет источник (engineering / user / both)
Use case 1: Test Strategy Merge
Input
- Output от test-researcher (engineering perspective)
- Output от user-perspective-critic (top-down)
Output: docs/test-strategy.md
# Test Strategy — feat-XXX
## Final Test List (after merge)
### t1: <name> (happy path) [from: engineering]
- Layer: runtime
- Verification: `npm test -- --filter=feat-XXX-t1`
- Negative-verify: ...
### t2: <name> (voice input) [from: user-perspective, добавлено]
- Layer: e2e
- Verification: ...
- Rationale: user-perspective-critic заметил что test-researcher не покрыл voice scenarios — это важно для русскоязычных пользователей
### t3-t7: ...
## Conflicts Resolved
### Conflict: test coverage for misspelling variants
- **Engineering said**: «фикс eval set — заменить опечатку на правильное написание»
- **User said**: «нет, это реальный кейс — система должна выдержать опечатки»
- **Resolution**: User wins — keep misspelling, add normalization layer
- **Action**: t4 проверяет normalization handles common typos
## Engineering-only items NOT in final
- <item>: rationale why excluded (e.g. mocked что не покрывает реальное поведение)
## User-perspective items NOT in final
- <item>: rationale why excluded (e.g. вне scope текущей фичи)
## Verification self-check plan (negative-test)
- t1: break by ... → тест должен упасть
- t2: ...
## Source attribution
- Engineering input: <link>
- User-perspective input: <link>
Process
- Read оба input файла
- Объединить тесты по категориям (happy / edge / error / e2e)
- При совпадении — merge в один тест с лучшим описанием
- При конфликте — user-perspective wins (record reason)
- Write
docs/test-strategy.md - Обновить
feature_list.json[active].verification.layer_1..4
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 fcaf24a0d7a3
- 1mo ago First seen · 148 lines · 62 tokens per session scan A 113d18b985ba
synthesizer is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 24d ago), licensed MIT. It adds 62 tokens to every session and 1,332 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
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…
property-author
Writes a property-based test from an Invariant declaration WITHOUT seeing the production implementation. Given only the invariant spec (type plus fn / inverse / oracle / invariant fields), the AC body, and the target function signature or type definitions, it authors a single property test file. Triggered by…
qa-report-reviewer-agent
Auto-Harness reviewer subagent for sprint QA report compliance. Use only immediately after evaluatorqa writes the current sprint QA report.
final-report-reviewer-agent
Auto-Harness reviewer subagent for final QA report compliance. Use only immediately after evaluatorfinal writes the final QA report.
retest-report-reviewer-agent
Auto-Harness reviewer subagent for sprint retest report compliance. Use only immediately after evaluatorretest writes the current sprint retest report.
evaluator-write-final-agent
Action-specific Auto-Harness Evaluator subagent for final report synthesis. Use only when the current legal action is evaluatorfinal.