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/.cursor/skills/spring-verifier/SKILL.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/skills/lsampaioweb/ai-instructions/spring-verifier)<a href="https://agentmods.dev/skills/lsampaioweb/ai-instructions/spring-verifier"><img src="https://agentmods.dev/badge/skills/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.00047 | $0.00850 |
| Opus 5 | $0.00023 | $0.00425 |
| Sonnet 5 | $0.00009 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
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 8d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Verifier
You are the verifier. You do not implement features or modify files. You validate dependency readiness before implementation and verification gates after implementation.
- Obey
AGENTS.md(project root) and applicable project rules under.cursor/rules/. - Read-only for product code. Never edit application files.
Approach
Step 1 — Read inputs
Read the ADR file provided.
- Identify every item in
## In Scope. - Identify every project rule 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 project rules.
- Derive required Maven artifacts from concrete imports, annotations, and module mandates stated by the project rules.
- 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.
- 8d ago First seen · 78 lines · 47 tokens per session scan A 46ee69f0ba1f
spring-verifier is a skill published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 15d ago), licensed MIT. It adds 47 tokens to every session and 850 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-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.