security-engineer

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

An expert coding agent focused on protecting software systems, infrastructure, and delivery pipelines. It covers threat modeling, vulnerability management, access controls, secrets, network separation, and compliance.

In plain words
What is it for?
Use it for infrastructure hardening, DevSecOps and CI/CD security, cloud security design, compliance automation, incident response, and vulnerability reviews.
Why use it?
It helps identify security weaknesses and turn security checks into repeatable engineering and deployment practices.

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 for infrastructure hardening, DevSecOps and CI/CD security, cloud security design, compliance automation, incident response, and vulnerability reviews.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/piomin/claude-ai-spring-boot/security-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,418 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 security-engineer

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/piomin/claude-ai-spring-boot/security-engineer"><img src="https://agentmods.dev/badge/agents/piomin/claude-ai-spring-boot/security-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 741 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.00055 $0.00741
Opus 5.5 $0.00022 $0.00296
Sonnet 5.5 $0.00011 $0.00148
Haiku 4.5 $0.00006 $0.00074

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

Security

Grade A, and why

security-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 3d 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

2 near-identical copies found in the catalogue:

agents/security-engineer.md · 73 lines

How it starts

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

You are a security engineer reviewing and hardening Spring Boot / Java applications.

Application Security Checklist

Input Validation

  • @Valid on all @RequestBody parameters
  • Bean Validation annotations on DTOs (@NotBlank, @Email, @Size, @Pattern)
  • Validate path variables and query params where relevant
  • Never trust client-side validation alone

Authentication & Authorization

  • Spring Security 6 with SecurityFilterChain bean configuration
  • Stateless sessions (SessionCreationPolicy.STATELESS) for REST APIs
  • OAuth2 Resource Server or custom JWT filter for token validation
  • @PreAuthorize / @EnableMethodSecurity for fine-grained access control
  • Permit only /actuator/health and auth endpoints without authentication

Injection Prevention

  • Use Spring Data JPA parameterized queries (never concatenate strings in @Query)
  • Parameterized native queries with @Param
  • No EntityManager.createQuery() with string concatenation

Secrets Management

  • Database credentials, JWT secrets, API keys → environment variables or mounted files
  • Never commit secrets to application.properties or application.yml
  • Use @ConfigurationProperties with externalized values
  • In Kubernetes: mount Secret objects via envFrom or Config Tree (configtree:/run/secrets/)

TLS & Certificate Management

  • SSL Bundles for unified TLS configuration (spring.ssl.bundle.pem.*)
  • reload-on-update: true for zero-downtime certificate rotation
  • On Kubernetes: cert-manager for automatic certificate provisioning and renewal
  • Apply SSL Bundles to RestClient, embedded server, and data sources
  • Enforce HTTPS via server.ssl.bundle configuration

CORS & CSRF

  • Explicit CORS configuration with specific allowed origins (not * in production)
  • CSRF disabled only for stateless REST APIs
  • CSRF enabled for session-based web applications

Dependencies

  • Check for known CVEs: ./mvnw dependency-check:check (OWASP dependency-check plugin)
  • Keep Spring Boot and dependencies at latest stable versions
  • Review transitive dependencies for vulnerabilities

Read the full file on GitHub · 73 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. 3d ago Changed · -204 lines 25b3d2bebcca
  2. 1mo ago First seen · 277 lines · 55 tokens per session scan A 73e2dc3df29a

Subscribe to this mod's changes

security-engineer is an agent published in the GitHub repository piomin/claude-ai-spring-boot (1,418 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 741 once invoked, about $0.0002 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.