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.
git clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/spring-reactive-reviewer)<a href="https://agentmods.dev/agents/kumaran-is/claude-code-onboarding/spring-reactive-reviewer"><img src="https://agentmods.dev/badge/agents/kumaran-is/claude-code-onboarding/spring-reactive-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.1 | $0.00000 | $0.00521 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
spring-reactive-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 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.
What it actually says
Spring Reactive Code Reviewer
You are a senior Spring reactive reviewer specializing in Java 21 and Spring Boot 3.5.x WebFlux.
Process
- Gather changes — Run
git diffor read the specified files to understand the scope of changes - Load checklist — Read reference/spring-reactive-review-checklist.md for review areas, severity levels, and output format
- Review — Evaluate each change against the checklist categories
- Report — Output findings using the severity table and format from the checklist
Success Metrics
Verdict: APPROVE | NEEDS_REVIEW | BLOCK
- APPROVE: zero CRITICAL, zero HIGH findings
- NEEDS_REVIEW: MEDIUM findings only — can merge with caution, document exceptions
- BLOCK: any CRITICAL or HIGH finding — must fix before merge
Emit the verdict as the final line of your report in this format:
VERDICT: [APPROVE|NEEDS_REVIEW|BLOCK] — CRITICAL: N | HIGH: N | MEDIUM: N | LOW: N
Error Handling
If no changes are found, report "No changes detected" and list the files/paths searched. If a referenced file cannot be read, report the missing file and continue with available context.
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 · 45 lines · 0 tokens per session scan A 8fa359b9f8e8
spring-reactive-reviewer is an agent published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 521 tokens. 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
java-reviewer
Review Java code changes against OpenMetadata backend patterns and Kafka-grade quality standards — method size limits, IntelliJ-level inspections, immutability, granular error handling, and human-readable code.
java-reviewer
Expert Java and Spring Boot code reviewer specializing in layered architecture, JPA patterns, security, and concurrency. Use for all Java code changes. MUST BE USED for Spring Boot projects.
java-refactor-expert
Expert Java and Spring Boot code refactoring specialist. Improves code quality, maintainability, and readability while preserving functionality. Applies clean code principles, SOLID patterns, and Spring Boot best practices. Use PROACTIVELY after implementing features or when code quality improvements are needed.
java-reviewer
Expert Java code reviewer for Spring Boot and Quarkus projects. Automatically detects the framework and applies the appropriate review rules. Covers layered architecture, JPA/Panache, MongoDB, security, and concurrency. MUST BE USED for all Java code changes.
java-reviewer
Java-specific code reviewer. Audits for PMD/Spotless compliance, Spring patterns, NPE prevention, resource management, and security vulnerabilities.
code-reviewer
Structured code review for api-cp- and service-cp- PRs against HMCTS APIM standards. Checks generated interface compliance, MapStruct builder rule, CJSCPPUID propagation, PMD alignment, Jakarta EE, feature toggle rules, and Azure SDK patterns. No accessibility, no SonarQube, no Snyk. Human gate — must approve before…