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 skills add a-pavithraa/springboot-skills-marketplace --skill code-reviewergit clone --depth 1 https://github.com/a-pavithraa/springboot-skills-marketplaceWrote 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/a-pavithraa/springboot-skills-marketplace/code-reviewer)<a href="https://agentmods.dev/skills/a-pavithraa/springboot-skills-marketplace/code-reviewer"><img src="https://agentmods.dev/badge/skills/a-pavithraa/springboot-skills-marketplace/code-reviewer/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/skills/a-pavithraa/springboot-skills-marketplace/code-reviewer"><img src="https://agentmods.dev/badge/skills/a-pavithraa/springboot-skills-marketplace/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.01577 |
| Opus 5 | $0.00041 | $0.00788 |
| Sonnet 5 | $0.00016 | $0.00315 |
| Haiku 4.5 | $0.00008 | $0.00158 |
Grade A, and why
code-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 12d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot 4 Reviewer (Java 17+)
Purpose
Use this skill to run a structured review of Spring Boot 4 code on any supported Java version (17 minimum; 21 LTS and 25 are common in greenfield Boot 4 projects). Keep findings grounded in the actual codebase and use the reference files only for the focus areas that apply.
Critical rules
- Never review without code context. Ask for files, diffs, or the relevant module if none is provided.
- Always cite file paths and line numbers for findings.
- Treat Spring Boot 4 as the target. Read the project's
pom.xml/build.gradleto determine the actual Java version (Boot 4 supports 17, 21, and 25). Do not flag Java 17 or 21 as "too old" — they are valid Boot 4 baselines. - Analyze workload before recommending virtual threads, reactive rewrites, or architecture changes.
- Use JSpecify as the preferred null-safety baseline for new Boot 4 code, but confirm whether the codebase is still in transition before flagging every legacy annotation.
- Prefer official Spring and Java guidance when a claim depends on framework behavior.
Workflow
Step 1: Confirm scope
Collect the minimum context required to review accurately:
- Scope: single file, module, PR, or full codebase.
- Target versions: confirm Java and Spring Boot versions from the build files when relevant.
- Focus areas: migration, architecture, data access, security, performance, null-safety, or all.
- Testing context: whether the user expects review findings only or also fix suggestions and test impact.
Step 2: Load only the references that match the review
Load references just in time:
| Focus | Read |
|---|---|
| Spring Boot 4 migration patterns and framework deltas | references/spring-boot-4-patterns.md |
| Java 25 language and concurrency adoption | references/java-25-features.md |
| Security review | references/security-checklist.md |
| Performance review | references/performance-patterns.md |
| Architecture boundaries and packaging | references/architecture-patterns.md |
| Domain model shape | references/domain-modeling.md |
| Value-object-heavy designs | references/value-objects-patterns.md |
| Null-safety checks | references/jspecify-null-safety.md |
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/architecture-patterns.md 33 KB
- references/domain-modeling.md 22 KB
- references/java-25-features.md 23 KB
- references/jspecify-null-safety.md 4.6 KB
- references/performance-patterns.md 20 KB
- references/security-checklist.md 18 KB
- references/spring-boot-4-patterns.md 26 KB
- references/value-objects-patterns.md 25 KB
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.
- 12d ago First seen · 188 lines · 82 tokens per session scan A cc3c5456ecfa
code-reviewer is a skill published in the GitHub repository a-pavithraa/springboot-skills-marketplace (75 stars, last pushed 17d ago), licensed MIT. It adds 82 tokens to every session and 1,577 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-30.
Other skills, from other repositories
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
auto-test-code
A structured process for critically reviewing and testing software code. It records review findings, test plans, commands, results, and supporting files in a project workspace.
git-pr-review
A read-only reviewer for GitHub pull requests, which are proposed code changes submitted for review. It produces an evidence-based report about whether a pull request should be merged.
review
Plan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.
code-reviewer
A code-review workflow that checks completed work against its requirements or plan before merging. It groups findings by severity and gives each issue a fix and a way to verify it.
flutter-dart-code-review
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.