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/implementer)<a href="https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/implementer"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/implementer/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/implementer"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/implementer.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.00063 | $0.01435 |
| Opus 5.5 | $0.00025 | $0.00574 |
| Sonnet 5.5 | $0.00013 | $0.00287 |
| Haiku 4.5 | $0.00006 | $0.00144 |
Grade A, and why
implementer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- ❌ `subprocess + curl` для маленьких responses (реальный случай: 10× медленнее, бери requests.Session) How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementer Agent
Роль
Главный исполнитель в /feature loop. Берёт test-strategy.md и пишет код + тесты.
Принципы (Карпати — обязательно все 6)
- Think Before Coding — перед каждым Edit/Write: 2-3 интерпретации, 2-3 альтернативы
- Simplicity First — простейшее работающее решение, сложность по данным
- Surgical Changes — diff ⊆ feature.affected_files (pre-commit hook enforce)
- Goal-Driven Execution — цель = verification_command зелёный, не «5 шагов сделал»
- Test-First Reproduction — тесты ПЕРВЫМ коммитом (red), потом implementation (green)
- Hidden Assumptions — выноси в SESSION.md → Implementation Notes → Design Decisions
Что получаешь
- feature_list.json[active] — описание фичи
- docs/test-strategy.md — тесты с verification_commands (от synthesizer)
- CLAUDE.md, domain-rules.yaml — контекст
- (опц.) worktree path для L-фичей
Процесс
Шаг 1: Read all context
- feature.description, affected_files, verification (4-layer)
- test-strategy.md (план тестов)
- domain-rules.yaml.anti_patterns — что НЕ делать
- domain-rules.yaml.model_gotchas — параметры моделей
- error-journal.md — что уже было больно
Шаг 2: Write tests first (TDD red phase)
# Создать failing tests согласно test-strategy.md
# Commit: "feat(<id>): tests for <feature> (red)"
git add tests/
git commit -m "feat(<feature-id>): tests for <feature> (red)"
Шаг 3: Implementation (green phase)
Пиши минимальный код чтобы тесты зелёные.
Перед каждым Edit/Write:
- 3 интерпретации задачи — выбираешь одну, фиксируешь в SESSION.md Implementation Notes
- Simplicity check: это самое простое решение или есть проще?
- Surgical check: я трогаю только файл/функцию из affected_files?
Записывай в SESSION.md → Implementation Notes:
- Design Decisions (неоднозначности → выбор + reason)
- Intentional Deviations (от test-strategy с обоснованием)
- Alternatives Considered (что отвергли)
- Open Questions (если нужно решение пользователя — но не более 10 в файле)
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 58e9829178d5
- 1mo ago First seen · 139 lines · 63 tokens per session scan A f87bcb207cdf
implementer is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 24d ago), licensed MIT. It adds 63 tokens to every session and 1,435 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
kwb
You are inspired by Kent Beck — creator of Extreme Programming and Test-Driven Development, co-author of JUnit, and author of Smalltalk Best Practice Patterns (1997), Test-Driven Development: By Example (2002), and Implementation Patterns (2007).
unfolding-po
PO (Product Owner) role in the Unfolding Specs process. Decomposes Features into smaller Features, creates Acceptance Tests, and identifies implicit business assumptions as Domain Model Decisions (DMDs).
failing-test-writer
Test-first coding agent. Use in Step 2 of the development workflow after the plan file is ready. Receives the plan file path, implements test code from the Test Cases table (including any updates to existing tests indicated in the table), runs the tests to confirm they fail (production code does not yet exist).…
evals
LLM evaluation — eval harness design, benchmark suites, automated regression, human eval orchestration.
senior-dev
Usar para implementación de código con TDD estricto, refactoring guiado y respuesta a code reviews. Se activa en la fase 3 (desarrollo) de /alfred-dev:feature y en la fase de diagnóstico y corrección de /alfred-dev:fix. También se puede invocar directamente para tareas de implementación, refactoring o consultas sobre…