What is validation-sample-builder?

An agent that builds a validation set: realistic test scenarios, expected results, and yes-or-no scoring for a product or feature.

Use it to create and run a 50–100-scenario validation sample before a feature cycle or final release, using product rules, user stories, research, and available real examples.

It provides a repeatable way to measure whether the current build handles real user situations, including normal, unusual, and error cases.

validation-sample-builder — Agent for Claude Code by andrewcigan

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/andrewcigan/vibe-dev-plugin

agentmods

npx agentmods add agents/andrewcigan/vibe-dev-plugin/validation-sample-builder

Made for: Claude Code.

Or install vibe-dev, the plugin that ships this one along with the rest of its 29 skills, 24 agents, 7 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/validation-sample-builder/github.svg)](https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/validation-sample-builder)

Your own site

<a href="https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/validation-sample-builder"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/validation-sample-builder/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/validation-sample-builder"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/validation-sample-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,609 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00061	$0.01609
Opus 5.5	$0.00024	$0.00644
Sonnet 5.5	$0.00012	$0.00322
Haiku 4.5	$0.00006	$0.00161

Measured 1mo ago against content hash 289a4048afc7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

agents/validation-sample-builder.md · 187 lines

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

Read the full file on GitHub · 187 lines

Changes

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 289a4048afc7
1mo ago First seen · 187 lines · 61 tokens per session scan A f6073d191986

Subscribe to this mod's changes

validation-sample-builder is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 24d ago), licensed MIT. It adds 61 tokens to every session and 1,609 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.

Claude Code Testing ai-agents claude-code-plugin harness vibe-coding

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…

hmj1026/dhpk · 155 tokens

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…

iroha924/mumei · 102 tokens

validation-sample-builder