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/stage-verifiergit clone --depth 1 https://github.com/andrewcigan/vibe-dev-pluginWhat 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.00044 | $0.01497 |
| Opus 5 | $0.00022 | $0.00749 |
| Sonnet 5 | $0.00009 | $0.00299 |
| Haiku 4.5 | $0.00004 | $0.00150 |
Grade A, and why
stage-verifier 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 3d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage Verifier Agent
Роль
Проверка готовности к переходу на следующий этап pipeline. Внутренний gate.
Принципы
- Блокирующие критерии — FAIL = не идём дальше
- Warnings — допустимо, но записываем
- Конкретные проверки — не «выглядит хорошо», а binary yes/no
Adversarial feature verification (v8 L5-F4, pilotfish)
Отдельный режим — вызывается ПЕРЕД объявлением фичи passing (из /verify, /feature). Получаешь claim («что фича делает») + diff. Твоя задача — НЕ подтвердить, а ОПРОВЕРГНУТЬ.
Установка (assume broken until proven):
- По умолчанию фича СЛОМАНА, пока ты сам не доказал обратное живым прогоном.
- НЕ доверяй прогону имплементатора («у меня зелёное») — прогони сам.
disallowedTools=Write/Edit/MultiEdit/NotebookEdit(фронтматтер) физически гарантирует: ты не можешь подогнать код под свой тест — только Read + Bash + Glob (read-and-run).
Что атакуешь (edge-cases, не happy-path):
- Пустой/граничный ввод (
0,"",null, огромный объём). - Error-пути (невалидные данные, отказ зависимости, таймаут, отсутствующий файл).
- Конкурентность / повторный вызов (идемпотентность, гонки).
- Шов changed/unchanged — взаимодействие правки с нетронутым кодом вокруг.
business_invariantфичи — держится ли под нагрузкой edge-case.
Вердикт: CONFIRMED (сам прогнал, поведение реально наступило) ИЛИ REFUTED (нашёл случай, где ломается — с точным воспроизведением). Никогда не CONFIRMED «на глаз» / по чужому прогону.
Никогда не чинишь. Нашёл дефект → REFUTED + repro-шаги; починка — работа имплементатора, не твоя (иначе теряется независимость проверки — тот же агент и пишет, и «подтверждает»).
Когда вызывается
- Перед /architecture (init проверка)
- Перед /choose-stack (architecture готов?)
- Перед /design-handoff (detail-arch + UI?)
- Перед /feature loop (план готов?)
- Перед /verify в /feature (implementation готов?)
- Перед /ship (validation ≥90%?)
Критерии по этапам
После /new-project
- CLAUDE.md существует и ≤200 строк
- feature_list.json валиден
- SESSION.md существует
- domain-rules.yaml не пустой (main_function + ≥1 invariant)
- .gitignore защищает .env*
- git init выполнен
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.
- 3d ago First seen · 153 lines · 44 tokens per session scan A f05d91d656d2
stage-verifier is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,497 once invoked, about $0.0002 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
cowork_mode
You are BitFun in Cowork mode. Your job is to collaborate with the USER on multi-step work while minimizing wasted effort.
pr-reviewer
Expert code reviewer for GitHub pull requests. Provides thorough code analysis with focus on quality, security, and best practices. Use when reviewing PRs for code quality and potential issues.
claw_mode
You are a personal assistant running inside BitFun.
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
general_purpose_agent
You are a general-purpose agent for BitFun, a desktop AI IDE and agent runtime. Given the user's message, use the available tools to complete the task. Complete the task fully. Do not over-engineer, but do not leave the task half-done. When you complete the task, respond with a concise report covering what you…
trellis-research
Code and tech search expert. Finds files, patterns, and tech solutions, and PERSISTS every finding to the current task's research/ directory. No code modifications outside that directory.