spring-boot-engineer

spring-boot-engineer is an agent for Claude Code from piomin/claude-ai-spring-boot. It costs 32 tokens per session (683 once invoked), scanned A, original, Apache-2.0.

A specialist agent for building Spring Boot 3 or newer Java applications, including microservices, cloud deployment, and reactive programming.

In plain words
What is it for?
Use it to review or build Spring Boot systems, plan microservice and cloud architectures, configure integrations, and check performance, security, testing, and documentation.
Why use it?
It helps organize decisions for large business applications that need integrations, production reliability, and support for modern Java deployment options.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the spring-boot-template plugin — 8 skills, 6 agents shipped together

Good fit Use it to review or build Spring Boot systems, plan microservice and cloud architectures, configure integrations, and check performance, security, testing, and documentation.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/piomin/claude-ai-spring-boot/spring-boot-engineer
About the project

piomin/claude-ai-spring-boot is a starter template for creating Spring Boot applications with Claude Code. Developers clone it as a structured foundation when using Claude Code to generate Spring Boot projects.

piomin/claude-ai-spring-boot · 1,427 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/piomin/claude-ai-spring-boot

Made for: Claude Code.

Or install spring-boot-template, the plugin that ships this one along with the rest of its 8 skills, 6 agents.

Wrote 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.

agentmods badge for spring-boot-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/piomin/claude-ai-spring-boot/spring-boot-engineer/github.svg)](https://agentmods.dev/agents/piomin/claude-ai-spring-boot/spring-boot-engineer)
Your own site
<a href="https://agentmods.dev/agents/piomin/claude-ai-spring-boot/spring-boot-engineer"><img src="https://agentmods.dev/badge/agents/piomin/claude-ai-spring-boot/spring-boot-engineer/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.

agentmods 80×15 button for spring-boot-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/piomin/claude-ai-spring-boot/spring-boot-engineer"><img src="https://agentmods.dev/badge/agents/piomin/claude-ai-spring-boot/spring-boot-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 683 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00683
Opus 5.5 $0.00013 $0.00273
Sonnet 5.5 $0.00006 $0.00137
Haiku 4.5 $0.00003 $0.00068

Measured 5d ago against content hash 26bdf3375bb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spring-boot-engineer 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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/spring-boot-engineer.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior Spring Boot engineer building production-ready Java applications. Follow these rules strictly.

Mandatory Rules

  • Use latest Spring Boot 4.x and Java 21+
  • Maven for dependency management; artifact name = parent directory name
  • Group ID: pl.piomin.services
  • No Lombok — write explicit constructors, getters, setters, LoggerFactory.getLogger()
  • Constructor injection only (no @Autowired on fields)
  • Write tests (positive and negative) for all generated code
  • Generate CI pipeline — detect existing CI setup or default to a sensible choice
  • Generate Docker Compose file for all components
  • Semantic versioning; bump PATCH on each new version
  • Update README.md on each new version

Architecture

src/main/java/pl/piomin/services/
├── controller/     # REST endpoints (@RestController, @Valid, @RequestMapping("/api/v1/..."))
├── service/        # Business logic (@Service, @Transactional)
├── repository/     # Data access (extends JpaRepository)
├── model/          # JPA entities (@Entity)
├── dto/            # Request/Response records
├── config/         # @Configuration, @ConfigurationProperties
└── exception/      # @RestControllerAdvice + custom exceptions

Key Patterns

  • @Transactional(readOnly = true) at class level for services, @Transactional on mutating methods
  • @Valid @RequestBody on all POST/PUT endpoints
  • DTOs as Java records for request/response objects
  • @RestControllerAdvice for global exception handling
  • Return ResponseEntity with proper status codes (201 Created, 204 No Content, etc.)
  • @ConfigurationProperties for type-safe config (no raw @Value for groups of properties)
  • RestClient for blocking HTTP calls to external services (not RestTemplate/WebClient)
  • @HttpExchange interfaces for declarative HTTP clients (replaces OpenFeign for simple cases)
  • OpenFeign remains a valid option when used with service discovery (Eureka/Consul) and load balancing

Default application.yml

Every new app should include these production-ready defaults:

Read the full file on GitHub · 76 lines

Changes

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.

  1. 5d ago Changed 26bdf3375bb4
  2. 7d ago Changed · -211 lines 09037a37918b
  3. 1mo ago First seen · 287 lines · 32 tokens per session scan A 9176b8f50ca0

Subscribe to this mod's changes

spring-boot-engineer is an agent published in the GitHub repository piomin/claude-ai-spring-boot (1,427 stars, last pushed 2d ago), licensed Apache-2.0. It adds 32 tokens to every session and 683 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other agents, from other repositories

java-developer

Implementación de código Java/Spring Boot siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en Java (controllers, services, repositories, entities, migraciones), se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de…

gonzalezpazmonica/pm-workspace · 77 tokens

java-pro

Master modern Java with streams, concurrency, and JVM optimization. Handles Spring Boot, reactive programming, and enterprise patterns. Use PROACTIVELY for Java performance tuning, concurrent programming, or complex enterprise solutions.

echoVic/blade-code · 44 tokens

java-software-architect-review

Provides expert Java software architecture review capability, specializing in Clean Architecture, Domain-Driven Design (DDD), and Spring Boot patterns. Reviews Java codebases for architectural integrity, proper bounded contexts, and SOLID principles. Use proactively when making Java architectural decisions, DDD…

giuseppe-trisciuoglio/developer-kit · 66 tokens

java-pro

Expert in modern, idiomatic Java and the JVM ecosystem. Use for Spring services, concurrency, streams, and migrating legacy Java to modern idioms.

JosephHampton/awesome-gemini-cli-subagents · 33 tokens

cap-service-developer

Use this agent when implementing CAP service handlers, CRUD operations, custom actions, and OData logic. This agent specializes in Node.js, TypeScript, and Java service development for CAP. Examples: "Implement a custom CREATE handler for Orders entity" "Add a bound action to mark order as completed" "How do I…

secondsky/sap-skills · 90 tokens

java-backend-engineer

Professional Java backend engineer. Use for building enterprise applications with Spring Boot, MyBatis, and Clean Architecture implementation.

ProjAnvil/MindForge · 28 tokens