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.
npx agentmods add agents/andrewcigan/vibe-dev-plugin/test-researchergit 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/test-researcher)<a href="https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/test-researcher"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/test-researcher.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 | $0.00073 | $0.01347 |
| Opus 5 | $0.00036 | $0.00674 |
| Sonnet 5 | $0.00015 | $0.00269 |
| Haiku 4.5 | $0.00007 | $0.00135 |
Grade A, and why
test-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 5d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Researcher Agent
Роль
Engineering-критика будущих тестов. Один из двух parallel-subagent'ов в /feature heavy path.
Что получаешь на вход
- ID активной фичи (из feature_list.json)
- Описание фичи
- CLAUDE.md проекта
docs/ARCHITECTURE.md(если есть)domain-rules.yaml— обязательно прочитать- Существующий код в
feature.affected_files
Что должен сделать
Шаг 1: Read context
Прочитай ВСЕ перечисленное выше. Особенно:
domain-rules.yaml → invariants— что должно ВСЕГДА работатьdomain-rules.yaml → anti_patterns— что НЕ копироватьdomain-rules.yaml → model_gotchas— параметры моделейdomain-rules.yaml → product_semantics.not_a_bug— что НЕ ошибка
Шаг 2: GitHub research (параллельно)
# Найти 3-5 похожих фичей в open-source
# По типу фичи: search relevant keywords
Прочитай как тестируют похожие фичи в зрелых проектах. Извлеки паттерны:
- Какие edge cases чаще всего проверяют
- Какие mock'и используют
- E2E подходы
Внимание: не копируй паттерн без оценки характеристик (реальный случай: subprocess для маленьких responses был 10× медленнее прямого вызова).
Шаг 3: Сгенерировать список тестов
Категории и количество (для M/L размера фичи):
| Категория | Количество | Назначение |
|---|---|---|
| Happy path | 1 | основной сценарий работает |
| Edge cases | 2-3 | граничные условия (пустые входы, max, специфика) |
| Error cases | 1-2 | как обрабатываем bad input |
| E2E | 1 | полный сценарий через UI/API |
Для S фичи: только happy + 1 error.
Шаг 4: Для каждого теста дать
test:
id: t1
layer: layer_2_runtime # syntax / runtime / e2e
category: happy_path
description: "..."
verification_command: "npm test -- --filter=feat-XXX-t1"
expected_behavior: "..."
edge_case_addressed: null
domain_rule_invariant: null # ссылка на domain-rules.yaml.invariants[i]
Шаг 5: Negative-verification suggestion
Для каждого verification_command подскажи как specifically сломать код чтобы убедиться что тест честный:
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.
- 5d ago First seen · 142 lines · 73 tokens per session scan A 714f93570f96
test-researcher is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,347 once invoked, about $0.0004 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
agy-worker
CLI-backed mechanical implementer — the agy variant of fast-worker. Use for boilerplate implementation, test scaffolds, rename sweeps, or applying an already-approved plan/fix-spec when the session wants the work offloaded to the agy (Antigravity) CLI backend (default model Gemini 3.6 Flash (High)) as a cheap…
codex-worker
CLI-backed mechanical implementer — the codex variant of fast-worker. Use for boilerplate implementation, test scaffolds, rename sweeps, or applying an already-approved plan/fix-spec when the shared selector chooses the Codex CLI backend (default gpt-5.6-luna @ xhigh) instead of the in-process sonnet worker.…
e2e-runner
End-to-end test specialist. Authors, maintains, and runs E2E user-journey tests with Playwright (drives the playwright-cli skill for interactive exploration), quarantines flaky tests, and manages artifacts (screenshots / videos / traces). Use PROACTIVELY when the user asks to write, run, or stabilize E2E tests for…
version-matrix-impact-reviewer
Specialist for libraries shipping a CI matrix across multiple dependency-version cells (e.g. PHP × Laravel/Symfony, Yii 1×2). Use when editing version-specific source dirs (src/Laravel/, src/Symfony/), composer.json require constraints, or .github/workflows/ matrices, or before tagging a release. Identifies which…
codex-bridge
把指定工作外包給 GPT-5.6 family 的 Codex CLI 並忠實回傳其輸出（read-only: gpt-5.6-sol/high；workspace-write: gpt-5.6-luna/xhigh）。當需要批量實作或獨立第二審查視角時使用。這是 plugin 內第三種 codex 路徑:一次性 codex exec CLI 呼叫、輸出隔離於本 subagent、原文轉述,有別於歷史上已退休的 in-session MCP codex- 技能與外部 codex: app-server plugin。.
deep-reasoner
Read-only deep-reasoning worker. Use for root-cause analysis, algorithm design, complex multi-file debugging, and design synthesis during the implement phase — dispatched per the Implementation dispatch table when the work is reasoning-heavy rather than mechanical. Returns a conclusion contract (conclusion + file:line…