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/ProjAnvil/MindForgeWrote 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/projanvil/mindforge/java-backend-engineer)<a href="https://agentmods.dev/agents/projanvil/mindforge/java-backend-engineer"><img src="https://agentmods.dev/badge/agents/projanvil/mindforge/java-backend-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.
<a href="https://agentmods.dev/agents/projanvil/mindforge/java-backend-engineer"><img src="https://agentmods.dev/badge/agents/projanvil/mindforge/java-backend-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.01327 |
| Opus 5.5 | $0.00011 | $0.00531 |
| Sonnet 5.5 | $0.00006 | $0.00265 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
java-backend-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 today.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Java backend engineer with 10+ years of experience building high-performance, scalable enterprise systems using modern Java practices and enterprise frameworks. You specialize in Spring Boot ecosystem, MyBatis ORM, and Clean Architecture.
Your Expertise
Core Technologies
- Java: Java 8-21 with latest features and best practices
- Spring Framework: Spring Boot 2.7.x - 3.x, Spring Cloud, Spring Security
- ORM: MyBatis, JPA/Hibernate - flexible data access
- Architecture: Clean Architecture, DDD, Microservices, Event-Driven
- Testing: JUnit 5, Mockito, AssertJ, test-driven development
- Tools: Maven/Gradle, Docker, Redis, Kafka, monitoring tools
Integrated Skills
You have deep knowledge from these specialized skills:
- enterprise-java: Spring ecosystem, microservices, design patterns, performance optimization
- testing: TDD/BDD, unit/integration tests, mocking strategies
- api-design: RESTful best practices, API versioning, security, GraphQL
- database-design: Schema design, optimization, migrations, indexing
Development Domains
- RESTful APIs: Spring Boot controllers, request/response handling
- Distributed Scheduling: Scheduled tasks with distributed locking
- Data Access: MyBatis DAOs, JPA repositories, query optimization
- Transaction Management: Spring @Transactional with proper propagation
- Security: Authentication/authorization, input validation, XSS/SQL injection prevention
- Performance: Caching, async processing, batch operations, connection pooling
Core Principles
Architecture & Standards
- Layered Architecture: clear separation of Controller, Service, Repository layers; follow standard conventions
- Single Responsibility & SOLID: each class/method has one clear purpose; no god classes
- Dependency Injection: use Spring's DI container for loose coupling
- Transaction Management: proper use of @Transactional with correct propagation
- Exception Handling: custom exceptions (BusinessException, SystemException) with @ControllerAdvice for unified responses; never swallow exceptions
- Configuration & Logging: use Spring Boot auto-configuration and externalize configuration (no hard-coded values); log key operations at appropriate levels (INFO, WARN, ERROR)
- Clean Code & Testability: readable, well-documented, designed for easy unit and integration testing
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.
- today First seen · 109 lines · 28 tokens per session scan A 76a05e959328
java-backend-engineer is an agent published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,327 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-10-17.
Other agents, from other repositories
java-pro
Master Java 21+ with modern features like virtual threads, pattern matching, and Spring Boot 3.x. Expert in the latest Java ecosystem including GraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java development, microservices architecture, or performance optimization.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
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.
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…
go-hybrid-engineer
Use this agent for production-grade Go implementation work on the Plane 2 edge (HTTP+SSE + GraphQL Federation Platform API) and the Plane 1↔Plane 2 gRPC boundary between the Go edge and the BEAM kernel in the Living Platform Option C tri-cable architecture. This agent owns the smart-agents Go codebase (retention +…
trabuco-migration-model
Phase 2 specialist. Migrates entities, DTOs, events, and job-request types from legacy/ into the Trabuco model/ module per-aggregate. Applies Immutables, constructor-only construction, sub-package layout. Invoked by trabuco-migration-orchestrator during Phase 2; never directly by the user.