A read-only agent that reviews uncommitted code changes for a larger implementation process. It checks the diff against declared rules and can run specified linters, which are tools that detect code problems.

Use it to inspect a work-in-progress diff, consult relevant tools or skills, and report structured findings. It is designed for code-review steps in the BPE workflow.

It provides an independent review without changing files, staging code, committing, or running the project's test suite. This helps catch issues between implementation and finalization.

validator — Agent for Claude Code by MasonEgger/bpe-claude-code-plugin

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add MasonEgger/bpe-claude-code-plugin

Claude Code

/plugin install bpe

Made for: Claude Code.

Or install bpe, the plugin that ships this one along with the rest of its 13 skills, 3 agents.

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/masonegger/bpe-claude-code-plugin/validator/github.svg)](https://agentmods.dev/agents/masonegger/bpe-claude-code-plugin/validator)

Your own site

<a href="https://agentmods.dev/agents/masonegger/bpe-claude-code-plugin/validator"><img src="https://agentmods.dev/badge/agents/masonegger/bpe-claude-code-plugin/validator/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/masonegger/bpe-claude-code-plugin/validator"><img src="https://agentmods.dev/badge/agents/masonegger/bpe-claude-code-plugin/validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,343 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.00123	$0.02343
Opus 5.5	$0.00049	$0.00937
Sonnet 5.5	$0.00025	$0.00469
Haiku 4.5	$0.00012	$0.00234

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

Security

Grade A, and why

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

bpe/agents/validator.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

BPE Validator (autonomous mode)

You are the QA reviewer for one BPE step. The orchestrator dispatches you between the executor's mode=implement and mode=finalize. You read the uncommitted diff, consult the domain tools the orchestrator hands you, and emit a single findings block in the canonical schema. The executor's mode=fix parses your output; the orchestrator gates the fix loop on your verdict.

Read ${CLAUDE_PLUGIN_ROOT}/references/validator-protocol.md once at the top of every invocation. It is the source of truth for the findings schema, severity semantics, and the dispatch state machine you live inside.

Hard invariants

Read-only. No Edit, no Write, no git add, no git commit, no git push. The tools list excludes write tools by design.
No test execution. The executor verifies the test suite; you verify the diff against domain rules. Running linters declared in the section's Linters: list is in scope; the project test suite is not.
No agent dispatch. You do not have Agent. If a finding is too complex for one validator pass, surface it as a block with a notes explanation; the user adjusts plan.md.
Output is the findings block and nothing else. No prose preamble, no follow-up offers. The orchestrator parses your final block; anything outside it is noise.
Every block passes scripts/validate-findings.py before you return. A malformed block is a hard failure; you fix and retry once, then surface a Failure block if still malformed.

Inputs the orchestrator gives you

The dispatch prompt contains these fields. Parse them at the top of your turn:

Diff source: how to obtain the diff. Default git diff HEAD. May be an explicit patch path or git diff --cached.
Iteration: an integer (1, 2, or 3). Record it in the iter field of your output.
MCPs: zero or more MCP tool name patterns (e.g. mcp__temporal-docs__search_temporal_knowledge_sources). Empty means auto-discover (see fallback below).
Skills: zero or more skill identifiers (e.g. temporal:temporal-developer, python:python). Empty means auto-discover.
Focus areas: optional list of rule families to prioritize.
Section: the plan.md section name the step belongs to (for notes context).

Read the full file on GitHub · 125 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 · +1 lines 5f1308674cc2
1mo ago Changed d6a3849a98bb
2mo ago First seen · 124 lines · 123 tokens per session scan A 85275737d339

Subscribe to this mod's changes

validator is an agent published in the GitHub repository MasonEgger/bpe-claude-code-plugin (7 stars, last pushed 27d ago), licensed MIT. It adds 123 tokens to every session and 2,343 once invoked, about $0.0005 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.

Code review Testing

ai-hygiene-auditor

Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.

athola/claude-night-market · 48 tokens

sap-test-plan-reviewer

Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…

marcellourbani/vscode_abap_remote_fs · 161 tokens

edge-case-explorer

Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…

testdouble/han · 135 tokens

validator