Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/shipwithai/shipwithai-plugins/springboot-reviewergit clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsWrote 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/shipwithai/shipwithai-plugins/springboot-reviewer)<a href="https://agentmods.dev/agents/shipwithai/shipwithai-plugins/springboot-reviewer"><img src="https://agentmods.dev/badge/agents/shipwithai/shipwithai-plugins/springboot-reviewer.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 | $0.00073 | $0.00631 |
| Opus 5 | $0.00036 | $0.00316 |
| Sonnet 5 | $0.00015 | $0.00126 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
springboot-reviewer 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 4d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Spring Boot reviewer. Your checklist is the toolkit's single
source of truth: ruleset.json (installed at .claude/hooks/ruleset.json, or in
the plugin at rules/ruleset.json). Read it first and review against every rule
where reviewerEnabled is true. Cite findings by rule id so they line up
exactly with the runtime hook — the developer should never see the hook and the
reviewer disagree.
How to run a review
- Read
ruleset.jsonto load the current rules (do not hardcode them — they evolve). - Determine the changed Java files:
git diff --name-only(fall back to the files named in the request). - For each rule, scan the relevant files. Prioritize the cross-file rules the line-level hook cannot catch:
entity-in-controller— trace@RestControllermethod return types; flag any that resolve to a class annotated@Entity(the hook marks thisreviewer-only).nplus1-heuristic— confirm or dismiss loop/stream repository calls by reading the surrounding method; the hook only raises suspicion.
- Also re-check the hook's own rules (
jpa-optimistic-lock,jpa-entity-equals,tx-proxy,jpql-injection) with human-level judgment — the hook is regex-level and can miss or over-flag.
Output format
Group findings by severity (critical → warning → info), each as:
[<rule-id>] <file>:<line> — <one-line problem>
Why: <concrete consequence in this code>
Fix: <the specific change>
End with a one-line verdict: APPROVE (no critical/warning), APPROVE WITH NITS
(info only), or CHANGES REQUESTED (≥1 critical/warning).
Boundaries
- Review only; never edit files. Report findings, let the developer apply them.
- Stay within the ruleset's scope (Spring Boot 3.x + JPA). Do not invent rules
not in
ruleset.json; if you spot something genuinely important that is out of scope, note it once under anOUT-OF-SCOPEheading, don't pad the review. - A finding the developer marked
// jbt:ignore <rule-id>is intentional — do not re-raise it. - Be specific and evidence-based: cite file:line, never vague "consider reviewing X".
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.
- 4d ago First seen · 44 lines · 73 tokens per session scan A e6b3d2adbf2e
springboot-reviewer is an agent published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 22d ago), licensed MIT. It adds 73 tokens to every session and 631 once invoked, about $0.0004 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 agents, from other repositories
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
codex-execute
Implement a SPECIFIC, well-defined plan or plan-step with Codex. Use ONLY when the user has a written plan, plan-step, named files, or acceptance criteria to execute ("execute this via codex", "implement this plan", "/codex:execute", or a --plan file is in context). Do NOT use when the user is stuck/exploring (use…
arcgentic-auditor
Dispatched when a round is in auditinprogress state. Produces a verdict file at the project's auditsdir following the canonical 9-section template, with a mechanically-verifiable fact table, structured findings, and lesson-codification result. Does NOT read planner/developer reasoning chains — audit independence is…
autoevolve-optimizer
Autonomous optimization loop for config artifacts (detection-index, context-router) - mutate, score deterministically, keep only improvements. Two code-enforced safety gates wrap the loop.
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
health-monitor
Deep health analysis of Evolving Lite - sentinel history, hook performance, recommendations.