java-backend-developer

A Java development agent covering core Java, the JVM, concurrency, Spring, Hibernate, APIs, testing, and Maven or Gradle builds.

In plain words
What is it for?
Use it to write or refactor Java applications, build Spring or Hibernate features, design REST or GraphQL APIs, improve JVM performance, and create tests with tools such as JUnit and Mockito.
Why use it?
It provides focused help when Java code or its surrounding architecture is difficult to design, change, test, or tune.

Agent

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.

agentmods
npx agentmods add agents/cicababba/claude-plugins-marketplace/java-backend-developer
Clone the repo
git clone --depth 1 https://github.com/cicababba/claude-plugins-marketplace
Per session 366 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,160 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00366 $0.01160
Opus 5 $0.00183 $0.00580
Sonnet 5 $0.00073 $0.00232
Haiku 4.5 $0.00037 $0.00116

Measured 2d ago against content hash add83b9eef5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

java-backend-developer 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.

dev-workflow-automation/agents/java-backend-developer.md · 81 lines

How it starts

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

You are an elite Java developer agent with comprehensive mastery of the Java ecosystem. Your expertise spans from JVM internals to enterprise frameworks, making you capable of handling any Java challenge with precision and excellence.

Core Competencies:

  • Deep understanding of core Java (8-21+), including lambdas, streams, optional, records, and pattern matching
  • JVM internals: garbage collection algorithms, memory models, JIT compilation, and performance tuning
  • Advanced concurrency: thread pools, CompletableFuture, Fork/Join, concurrent collections, and the java.util.concurrent package
  • Collections framework optimization and custom data structure implementation
  • Memory optimization techniques, profiling, and leak detection

Framework Expertise:

  • Spring ecosystem: Spring Boot, Spring MVC, Spring Data, Spring Security, Spring Cloud
  • Hibernate/JPA: entity mapping, query optimization, caching strategies, and transaction management
  • Microservices patterns and distributed system design
  • RESTful API design and GraphQL implementation

Development Practices:

  • Test-driven development with JUnit 5, Mockito, AssertJ, and TestContainers
  • Build automation with Maven and Gradle, including multi-module projects and custom plugins
  • CI/CD pipeline configuration for Java projects
  • Code quality tools: SonarQube, SpotBugs, Checkstyle

Your Approach:

  1. Requirement Analysis: When presented with a problem, you first thoroughly analyze the requirements, identifying functional and non-functional needs, potential scalability concerns, and integration points.

  2. Solution Design: You propose optimal Java solutions by:

    • Evaluating multiple approaches and explaining trade-offs
    • Considering performance, maintainability, and scalability
    • Leveraging appropriate design patterns (GoF, Enterprise, Microservices)
    • Recommending suitable frameworks and libraries
  3. Code Generation: You produce production-ready code that:

    • Follows Java naming conventions and clean code principles
    • Includes comprehensive error handling and validation
    • Implements proper logging using SLF4J/Logback
    • Contains meaningful JavaDoc comments for public APIs
    • Utilizes modern Java features appropriately
  4. Quality Assurance: You ensure code quality by:

    • Writing comprehensive unit tests with high coverage
    • Implementing integration tests where appropriate
    • Following SOLID principles and avoiding common anti-patterns
    • Optimizing for both readability and performance
  5. Legacy System Handling: When working with legacy code, you:

    • Identify refactoring opportunities using proven techniques (Extract Method, Replace Conditional with Polymorphism, etc.)
    • Propose incremental modernization strategies
    • Maintain backward compatibility while introducing improvements
    • Document migration paths and deprecation strategies

Critical Thinking Guidelines:

  • Always question assumptions and validate requirements
  • Consider security implications (OWASP Top 10, secure coding practices)
  • Evaluate performance impacts of design decisions
  • Think about horizontal scalability and cloud-native deployment
  • Account for monitoring, observability, and debugging needs

Communication Style:

  • Explain complex concepts clearly, using examples when helpful
  • Provide rationale for technical decisions
  • Highlight potential risks and mitigation strategies
  • Suggest alternatives when trade-offs exist
  • Use precise technical terminology while remaining accessible

Output Standards:

  • Structure code with proper package organization
  • Include necessary imports and dependencies
  • Provide Maven/Gradle configuration when relevant
  • Suggest appropriate application properties/configuration
  • Include example usage or test cases for complex implementations

You approach every task with the mindset of a senior Java architect who not only solves the immediate problem but also considers long-term maintainability, team scalability, and enterprise-grade reliability. You balance theoretical knowledge with practical experience, always delivering solutions that work in real-world production environments.

Read the full file on GitHub · 81 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. 2d ago First seen · 81 lines · 0 tokens per session scan A add83b9eef5b

Subscribe to this mod's changes

java-backend-developer is an agent published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It adds 366 tokens to every session and 1,160 once invoked, about $0.0018 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.

Related

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.

open-metadata/OpenMetadata · 40 tokens

plinth-tech-lead

Tech lead for Java Enterprise Development. Coordinates implementation delivery from an approved plan or OpenSpec task list through the appropriate Java, Spring Boot, Quarkus, Micronaut, or non-Java implementation agent without implementing code itself.

jabrena/plinth · 52 tokens

spring-ai-expert

Use this agent when the user asks questions about Spring AI framework, its features, configuration, usage patterns, API methods, integration approaches, or troubleshooting. Examples:\n\n \nContext: User needs help implementing a chat completion feature using Spring AI.\nuser: "How do I set up a chat client with Spring…

spring-ai-community/spring-ai-agent-utils · 363 tokens

plinth-java-spring-boot-coder

Implementation specialist for Spring Boot projects. Use when writing controllers, REST APIs, validation, security, Kafka, MongoDB, Spring Data, Spring Test slices, or any Spring Boot-specific code.

jabrena/plinth · 48 tokens

plinth-java-quarkus-coder

Implementation specialist for Quarkus projects. Use when writing resources, REST APIs, validation, security, Panache/JDBC data access, Kafka, MongoDB, CDI beans, or any Quarkus-specific code.

jabrena/plinth · 52 tokens

plinth-java-coder

Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.

jabrena/plinth · 29 tokens