validar

validar is a skill for Claude Code from igoruehara/spec-driven. It costs 76 tokens per session (505 once invoked), scanned A, original, MIT.

A post-implementation acceptance-testing process that checks whether a feature matches its written specification. It maps each AC-N, or acceptance criterion, to tests and checks the project's completion rules.

In plain words
What is it for?
Running the project's test gates after implementation, checking every acceptance criterion and decision-matrix case, resolving specification deviations, and updating project state documentation.
Why use it?
It provides evidence that the feature works instead of relying only on code inspection. It also exposes missing tests, failed checks, unresolved differences from the specification, and incomplete documentation.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; mentions Claude Code.

Good fit Running the project's test gates after implementation, checking every acceptance criterion and decision-matrix case, resolving specification deviations, and updating project state documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/igoruehara/spec-driven/validar
Install

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.

Any agent
npx skills add igoruehara/spec-driven --skill validar
Clone the repo
git clone --depth 1 https://github.com/igoruehara/spec-driven

Made for: Claude Code.

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.

agentmods badge for validar

README.md
[![agentmods](https://agentmods.dev/badge/skills/igoruehara/spec-driven/validar/github.svg)](https://agentmods.dev/skills/igoruehara/spec-driven/validar)
Your own site
<a href="https://agentmods.dev/skills/igoruehara/spec-driven/validar"><img src="https://agentmods.dev/badge/skills/igoruehara/spec-driven/validar/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.

agentmods 80×15 button for validar

Your own site · 80×15
<a href="https://agentmods.dev/skills/igoruehara/spec-driven/validar"><img src="https://agentmods.dev/badge/skills/igoruehara/spec-driven/validar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 505 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.00505
Opus 5.5 $0.00030 $0.00202
Sonnet 5.5 $0.00015 $0.00101
Haiku 4.5 $0.00008 $0.00051

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

Security

Grade A, and why

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

template/.claude/skills/validar/SKILL.md · 29 lines

What it actually says

Skill: Validar feature (UAT)

Fecha o loop SDD: prova que a implementação cumpre a spec, pelo gate executável — não por inspeção. Rode depois de implementar (pode ser em outra sessão).

Processo

  1. Identifique a feature (specs/NNNN-<nome>/) e leia spec.md + tasks.md.
  2. Rode os gates de docs/engineering/TESTING.md (e os comandos da coluna Gate do tasks.md). O /verify embutido do Claude Code ajuda a validar comportamento real.
  3. Mapeie AC-N → teste e mostre a tabela; aponte qualquer AC sem cobertura ou falhando. Se a spec tem Matriz de decisão, cada linha é um caso de teste: confira que toda linha tem teste correspondente (combinações são onde mais escapa bug).
  4. SPEC_DEVIATION: resolva os pendentes — ou corrige o código (a spec vence) ou atualiza a spec conscientemente (e registra ADR se for difícil de reverter). Se a decisão "corrigir vs atualizar" tiver ramificações (afeta outros AC, fronteiras, ADRs), rode /clarificar para fechar a árvore antes de escolher.
  5. Definition of Done (ver README.md / CLAUDE.md): AC verdes pelo gate, sem deviation aberto, ADRs registrados, glossário/context-map atualizados, spec fiel.
  6. Atualize docs/STATE.md (próximo passo / decisões) — ou rode /handoff para encerrar.

Saída

Veredito claro: pronto para merge ou a lista do que falta (AC sem cobertura, deviation aberto, item de DoD pendente). Se há MCP de escrita validado, ofereça atualizar a issue/página da feature.

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.

  1. 1mo ago First seen · 29 lines · 76 tokens per session scan A 7e88023426f9

Subscribe to this mod's changes

validar is a skill published in the GitHub repository igoruehara/spec-driven (213 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 505 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens