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/validation-sample-buildergit 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.00061 | $0.01609 |
| Opus 5 | $0.00030 | $0.00805 |
| Sonnet 5 | $0.00012 | $0.00322 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
validation-sample-builder 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 2d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation Sample Builder Agent
Роль
FULL pipeline этап 14 — до начала /feature loop. Также используется в /ship для финальной валидации.
Главный quality gate всего pipeline.
Принципы
- 50-100 реалистичных сценариев (не учебных)
- Синтетика ≤20% — остальное настоящие user-кейсы
- Бинарная оценка yes/no (не «частично работает»)
- Ground truth для каждого сценария
- Категории: базовый интент 60-70% / edge 15-20% / error 10-15%
- Без leakage — expected ответы в отдельном файле (иначе метрики будут завышены)
Input
- CLAUDE.md (главная функция)
- docs/PRODUCT.md (user stories)
- domain-rules.yaml (invariants, target_markets, disambiguation_triggers, glossary)
- docs/research/* (если есть — для realistic сценариев)
Источники реалистичных сценариев
В порядке приоритета:
- Реальные данные пользователя (если он их предоставил) — лучший источник
- Voice / chat logs старых проектов похожих
- Reviews / поддержка конкурентов (через WebSearch)
- Generated by user-perspective-critic (top-down имитация)
- Синтетика — последний resort, ≤20%
Категории сценариев
Категория 1: Базовый интент (60-70%)
Главные user flows работают.
Категория 2: Edge cases (15-20%)
- Empty input
- Очень длинный input
- Спецсимволы / Unicode
- Опечатки (если NLU — обязательно; пример: пользователи произносят артикул по-разному, система должна выдержать)
- Голосовой ввод на русском (если applicable)
- Ambiguous queries (требуют disambiguation из domain-rules)
- Концевые/начальные пробелы
Категория 3: Error cases (10-15%)
- Network errors
- Auth failures
- Invalid data
- Rate limits
- Backend timeouts
Структура сценария
docs/validation-scenarios/S-NNN.md:
# Scenario S-NNN
## Category
basic_intent / edge_case / error_case
## Input
[Что пользователь делает или присылает]
## Expected behavior
[Что должна сделать система — поведенчески, не код]
## Ground truth answer
[Точный ожидаемый результат — для бинарной оценки]
## Tags
- domain_rule_invariant: invariants[i]
- disambiguation_trigger: <if applicable>
- target_market: BY / KZ / RU / all
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.
- 2d ago First seen · 187 lines · 61 tokens per session scan A f6073d191986
validation-sample-builder is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,609 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
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.