Borrowing it
Nothing to install: this file belongs to lsampaioweb/ai-instructions. 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/lsampaioweb/ai-instructions/main/.github/agents/spring-verifier.agent.mdgit clone --depth 1 https://github.com/lsampaioweb/ai-instructionsWrote 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/lsampaioweb/ai-instructions/spring-verifier)<a href="https://agentmods.dev/agents/lsampaioweb/ai-instructions/spring-verifier"><img src="https://agentmods.dev/badge/agents/lsampaioweb/ai-instructions/spring-verifier.svg" alt="Measured on agentmods" 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.00041 | $0.00796 |
| Opus 5 | $0.00020 | $0.00398 |
| Sonnet 5 | $0.00008 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
Spring 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 3d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the verifier agent. You do not implement features or modify files. You validate dependency readiness before implementation and verification gates after implementation.
Approach
Step 1 — Read inputs
Read the ADR file provided.
- Identify every item in
## In Scope. - Identify every instruction file referenced by the ADR.
- Identify whether the caller provided a list of created or modified files.
Step 2 — Dependency preflight
Build a dependency checklist from the ADR and referenced instruction files.
- Derive required Maven artifacts from concrete imports, annotations, and module mandates stated by the instruction files.
- Verify each required artifact is already declared in
pom.xml. - If a required artifact is missing: respond with
STATUS: FAILand emitISSUESentries prefixed withDEPENDENCY_GAP, then stop.
Step 3 — Pre-implementation exit
If no created or modified file list was provided, stop after dependency preflight and respond with STATUS: PASS.
Step 4 — Build gate
Run mvn clean compile -DskipTests from the project root.
- If compilation succeeds: continue.
- If compilation fails with dependency or network-resolution signatures: respond with
STATUS: FAILand emitISSUESentries prefixed withENVIRONMENT_BLOCKEDincluding the failing command and concrete signature, then stop. - If compilation fails for code reasons: respond with
STATUS: FAILand emitISSUESentries prefixed withBUILD_FAILincluding the failing command and concrete compiler output, then stop.
Step 5 — Test gate
Run mvn test -DskipITs from the project root.
- If tests succeed: continue.
- If tests fail with dependency or network-resolution signatures, or SGBD-unavailable signatures: respond with
STATUS: FAILand emitISSUESentries prefixed withENVIRONMENT_BLOCKEDincluding the failing command and concrete signature, then stop. - If tests fail for code reasons: respond with
STATUS: FAILand emitISSUESentries prefixed withTEST_FAILincluding the failing command and concrete test output, then stop.
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.
- 3d ago First seen · 69 lines · 41 tokens per session scan A 3038f715cc66
Spring Verifier is an agent published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 14d ago), licensed MIT. It adds 41 tokens to every session and 796 once invoked, about $0.0002 per session on Opus 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-09-03.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…
canary-test-healer
Diagnose and fix a consistently-failing test. Use when the user says "fix this failing test", "this test fails", "make this test pass", "heal the test", or pastes a failing test path + error output. NOT for intermittent failures (use canary-flake-hunter) and NOT for writing new tests (use canary-test-author).
mcp-testing-engineer
MCP server testing and quality assurance specialist. Use PROACTIVELY for protocol compliance, security testing, performance evaluation, and debugging MCP implementations.