# validator

The validator subagent checks a task against its acceptance criteria and reports issues. Run it after a builder agent finishes its work.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 3990 repo stars
- Author: disler
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/disler/claude-code-hooks-mastery/tree/HEAD/.claude/agents/team/validator.md
- Updated: 2026-03-04
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/validator

## What it does

\`validator` handles one task at a time. It reads the task details and acceptance criteria with `TaskGet`, then examines relevant files and command output. When the task calls for tests, type checks, or linting, it runs those checks and compares the results with the stated requirements.

The agent is read-only: it reports problems but cannot change files. Once its review is done, it marks the task complete with `TaskUpdate` and records the status, checks performed, and findings. Any fixes must come from another agent or a person.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/validator.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/validator.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/validator.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/disler/claude-code-hooks-mastery/tree/HEAD/.claude/agents/team/validator.md

## When to use it
- check whether a task meets its acceptance criteria
- spot missing or incorrect changes in relevant files
- run requested checks and record their results
- save a validation status with `TaskUpdate`

## Example prompts
- Ask the `validator` subagent to check the task against its acceptance criteria.
- Review the builder’s changes and run the tests required by the task.
- Compare the result with the requirements and report any failed checks.

## Similar
- [Skill Validator](https://affpapa.org/en/nevibecode/skills/skill-validator.md) — skill · 131 installs
- [impl-validator](https://affpapa.org/en/nevibecode/skills/impl-validator.md) — skill · 2300 installs
- [reference-analysis-validator](https://affpapa.org/en/nevibecode/skills/reference-analysis-validator.md) — skill · 1500 installs
- [simulation-validator](https://affpapa.org/en/nevibecode/skills/simulation-validator.md) — skill · ★ 95 repo stars
- [vastlint - IAB XML VAST validator and linter](https://affpapa.org/en/nevibecode/mcp/vastlint-iab-xml-vast-validator-and-linter.md) — MCP server · 404 installs
- [poc-validator](https://affpapa.org/en/nevibecode/agents/poc-validator.md) — subagent · ★ 2482 repo stars

## Other versions with the same name
- [validator · h-mmer](https://affpapa.org/en/nevibecode/agents/h-mmer-validator.md) — ★ 1298 repo stars
- [validator · tubelabhq](https://affpapa.org/en/nevibecode/agents/tubelab-validator.md) — ★ 288 repo stars

From the same set: [disler/claude-code-hooks-mastery](https://affpapa.org/en/nevibecode/by/disler/claude-code-hooks-mastery.md) — 25 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
