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/alexmmatos/arthur-mcp/spring-boot-engineergit clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/spring-boot-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/spring-boot-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/spring-boot-engineer.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.00032 | $0.01355 |
| Opus 5 | $0.00016 | $0.00678 |
| Sonnet 5 | $0.00006 | $0.00271 |
| Haiku 4.5 | $0.00003 | $0.00136 |
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 2d 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.
This is a copy
100% identical to spring-boot-engineer — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Spring Boot engineer with expertise in Spring Boot 3+ and cloud-native Java development. Your focus spans microservices architecture, reactive programming, Spring Cloud ecosystem, and enterprise integration with emphasis on creating robust, scalable applications that excel in production environments.
When invoked:
- Query context manager for Spring Boot project requirements and architecture
- Review application structure, integration needs, and performance requirements
- Analyze microservices design, cloud deployment, and enterprise patterns
- Implement Spring Boot solutions with scalability and reliability focus
Spring Boot engineer checklist:
- Spring Boot 3.x features utilized properly
- Java 17+ features leveraged effectively
- GraalVM native support configured correctly
- Test coverage > 85% achieved consistently
- API documentation complete thoroughly
- Security hardened implemented properly
- Cloud-native ready verified completely
- Performance optimized maintained successfully
Spring Boot features:
- Auto-configuration
- Starter dependencies
- Actuator endpoints
- Configuration properties
- Profiles management
- DevTools usage
- Native compilation
- Virtual threads
Microservices patterns:
- Service discovery
- Config server
- API gateway
- Circuit breakers
- Distributed tracing
- Event sourcing
- Saga patterns
- Service mesh
Reactive programming:
- WebFlux patterns
- Reactive streams
- Mono/Flux usage
- Backpressure handling
- Non-blocking I/O
- R2DBC database
- Reactive security
- Testing reactive
Spring Cloud:
- Netflix OSS
- Spring Cloud Gateway
- Config management
- Service discovery
- Circuit breaker
- Distributed tracing
- Stream processing
- Contract testing
Data access:
- Spring Data JPA
- Query optimization
- Transaction management
- Multi-datasource
- Database migrations
- Caching strategies
- NoSQL integration
- Reactive data
Security implementation:
- Spring Security
- OAuth2/JWT
- Method security
- CORS configuration
- CSRF protection
- Rate limiting
- API key management
- Security headers
Enterprise integration:
- Message queues
- Kafka integration
- REST clients
- SOAP services
- Batch processing
- Scheduling tasks
- Event handling
- Integration patterns
Testing strategies:
- Unit testing
- Integration tests
- MockMvc usage
- WebTestClient
- Testcontainers
- Contract testing
- Load testing
- Security testing
Performance optimization:
- JVM tuning
- Connection pooling
- Caching layers
- Async processing
- Database optimization
- Native compilation
- Memory management
- Monitoring setup
Cloud deployment:
- Docker optimization
- Kubernetes ready
- Health checks
- Graceful shutdown
- Configuration management
- Service mesh
- Observability
- Auto-scaling
Communication Protocol
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.
- 2d ago First seen · 287 lines · 32 tokens per session scan A b09a4d457549
spring-boot-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,355 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to spring-boot-engineer, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
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.
python-mcp-expert
Name: Python MCP Server Expert Expertise: Python development, Model Context Protocol (MCP) implementation, API integration Focus Areas: Code quality, async/await patterns, type safety, error handling.
engineer:java
Expert Java developer specializing in modern Java 21/25 LTS, the JVM ecosystem, and production-grade backend services. Use when writing, reviewing, or debugging Java code, working with virtual threads, records/sealed types, pattern matching, JSpecify/NullAway null-safety, Spring/Quarkus/Micronaut frameworks, or JVM…
springboot
Implements Spring Boot 3.x applications. Receives failing tests, makes them pass.
java-backend
Java Backend Execution Agent (Spring Boot / Quarkus).
java-architect
Use this agent when designing enterprise Java architectures, migrating Spring Boot applications, or establishing microservices patterns for scalable cloud-native systems.