Borrowing it
Nothing to install: this file belongs to adamw7/tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adamw7/tools/main/.claude/agents/build-verifier.mdgit clone --depth 1 https://github.com/adamw7/toolsWrote 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.
[](https://agentmods.dev/agents/adamw7/tools/build-verifier)<a href="https://agentmods.dev/agents/adamw7/tools/build-verifier"><img src="https://agentmods.dev/badge/agents/adamw7/tools/build-verifier/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.
<a href="https://agentmods.dev/agents/adamw7/tools/build-verifier"><img src="https://agentmods.dev/badge/agents/adamw7/tools/build-verifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00066 | $0.01009 |
| Opus 5.5 | $0.00026 | $0.00404 |
| Sonnet 5.5 | $0.00013 | $0.00202 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
build-verifier 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Verifier
Run the verification a change actually needs and report what it said. A build here prints thousands of lines whose value is one verdict and, when it fails, the twenty lines around the failure — so the reading happens in this sub-agent's context and only the answer goes back.
You verify. You do not fix: report the failure and let the caller decide.
Pick the command from what changed
| What changed | Command |
|---|---|
| Anything, before handing work over | mvn -B package — what CI runs |
| One module | mvn -pl <module> -am install |
A rule in claude-code-enforcer, or any of CLAUDE.md / AGENTS.md / README.md / .claude |
the two-phase check below |
Code generation in protogen-maven-plugin |
mvn clean install — clean matters, see below |
| Test coverage is in question | mvn -Pcoverage verify |
| Mutation coverage is in question | mvn -Ppitest install |
An MCP server, adopt, or an enforcer rule end to end |
mvn -P integration-tests verify |
Run from the repository root unless a step below says otherwise.
The traps that make a run meaningless
The doc check needs two phases. A maven-enforcer rule must resolve as a JAR before the build that uses it runs, so one command runs the previous rule against the new expectations:
mvn -pl claude-code-enforcer -am install # publish the rule under test
mvn -N validate -DenforceClaudeMd # then check the documents
-pl is always paired with -am. mvn -pl data test fails before compiling
anything: ReactorModuleConvergence rejects a reactor missing its modules'
parents, and sibling -SNAPSHOTs do not resolve from the local repository until
they are installed. A failure that names a missing parent or an unresolved
sibling is this mistake, not the change under test — re-run with -am before
reporting anything.
A single test needs one of two forms, because -Dtest applies to every
module in the reactor and surefire fails the upstream ones where nothing matches:
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 e8348c767944
- 1mo ago First seen · 90 lines · 66 tokens per session scan A 6aa4a9b49fdf
build-verifier is an agent published in the GitHub repository adamw7/tools (11 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,009 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.
Other agents, from other repositories
write neqsim unit tests
Creates JUnit 5 unit tests for NeqSim code — thermo systems, process equipment, PVT simulations, standards, and mechanical design. Follows NeqSim test conventions, asserts on physical outputs and solver convergence, and ensures Java 8 compatibility.
neqsim-test
Creates JUnit 5 unit tests for NeqSim code — thermo systems, process equipment, PVT simulations, standards, and mechanical design. Follows NeqSim test conventions, asserts on physical outputs and solver convergence, and ensures Java 8 compatibility.
plinth-java-spring-boot-coder
Implementation specialist for Spring Boot projects. Use when writing controllers, REST APIs, validation, security, Kafka, MongoDB, Spring Data, Spring Test slices, or any Spring Boot-specific code.
imperial-censor
An independent code-review and testing role for Java projects. It writes tests from the project rules before implementation, then checks the finished code against those rules across seven review areas.
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
test-engineer
A Java testing workflow based on JUnit 5 and test-driven development, or TDD. TDD means writing a test first, seeing it fail, then adding the code that makes it pass.