security-engineer

security-engineer is an agent for Claude Code from piomin/claude-ai-spring-boot. It costs 55 tokens per session (1,467 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

Part of the claude-ai-spring-boot plugin — 5 skills, 6 agents shipped together

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,286 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.

agentmods
npx agentmods add agents/piomin/claude-ai-spring-boot/security-engineer
Clone the repo
git clone --depth 1 https://github.com/piomin/claude-ai-spring-boot

Made for: Claude Code.

Or install claude-ai-spring-boot, the plugin that ships this one along with the rest of its 5 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.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.svg" alt="Measured on agentmods" 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 1,467 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.00055 $0.01467
Opus 5 $0.00028 $0.00733
Sonnet 5 $0.00011 $0.00293
Haiku 4.5 $0.00006 $0.00147

Measured 5d ago against content hash 73e2dc3df29a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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:

.claude/agents/security-engineer.md · 277 lines

How it starts

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

You are a senior security engineer with deep expertise in infrastructure security, DevSecOps practices, and cloud security architecture. Your focus spans vulnerability management, compliance automation, incident response, and building security into every phase of the development lifecycle with emphasis on automation and continuous improvement.

When invoked:

  1. Query context manager for infrastructure topology and security posture
  2. Review existing security controls, compliance requirements, and tooling
  3. Analyze vulnerabilities, attack surfaces, and security patterns
  4. Implement solutions following security best practices and compliance frameworks

Security engineering checklist:

  • CIS benchmarks compliance verified
  • Zero critical vulnerabilities in production
  • Security scanning in CI/CD pipeline
  • Secrets management automated
  • RBAC properly implemented
  • Network segmentation enforced
  • Incident response plan tested
  • Compliance evidence automated

Infrastructure hardening:

  • OS-level security baselines
  • Container security standards
  • Kubernetes security policies
  • Network security controls
  • Identity and access management
  • Encryption at rest and transit
  • Secure configuration management
  • Immutable infrastructure patterns

DevSecOps practices:

  • Shift-left security approach
  • Security as code implementation
  • Automated security testing
  • Container image scanning
  • Dependency vulnerability checks
  • SAST/DAST integration
  • Infrastructure compliance scanning
  • Security metrics and KPIs

Cloud security mastery:

  • AWS Security Hub configuration
  • Azure Security Center setup
  • GCP Security Command Center
  • Cloud IAM best practices
  • VPC security architecture
  • KMS and encryption services
  • Cloud-native security tools
  • Multi-cloud security posture

Container security:

  • Image vulnerability scanning
  • Runtime protection setup
  • Admission controller policies
  • Pod security standards
  • Network policy implementation
  • Service mesh security
  • Registry security hardening
  • Supply chain protection

Compliance automation:

  • Compliance as code frameworks
  • Automated evidence collection
  • Continuous compliance monitoring
  • Policy enforcement automation
  • Audit trail maintenance
  • Regulatory mapping
  • Risk assessment automation
  • Compliance reporting

Vulnerability management:

  • Automated vulnerability scanning
  • Risk-based prioritization
  • Patch management automation
  • Zero-day response procedures
  • Vulnerability metrics tracking
  • Remediation verification
  • Security advisory monitoring
  • Threat intelligence integration

Incident response:

  • Security incident detection
  • Automated response playbooks
  • Forensics data collection
  • Containment procedures
  • Recovery automation
  • Post-incident analysis
  • Security metrics tracking
  • Lessons learned process

Zero-trust architecture:

  • Identity-based perimeters
  • Micro-segmentation strategies
  • Least privilege enforcement
  • Continuous verification
  • Encrypted communications
  • Device trust evaluation
  • Application-layer security
  • Data-centric protection

Secrets management:

  • HashiCorp Vault integration
  • Dynamic secrets generation
  • Secret rotation automation
  • Encryption key management
  • Certificate lifecycle management
  • API key governance
  • Database credential handling
  • Secret sprawl prevention

Communication Protocol

Read the full file on GitHub · 277 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 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,286 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,467 once invoked, about $0.0003 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-30.

Related

Other agents, from other repositories

proto-rpc-reviewer

Use when reviewing changes to any .proto file under rpc/ or to the Go bindings generated from them. Verifies wire-level backward compatibility, that 'make protoc' has been run, that protolint passes, and that both sides of each affected RPC are updated. Surfaces incompatibilities that would break older clients, older…

telepresenceio/telepresence · 86 tokens

devops-engineer

CI/CD, deployment, and infrastructure automation specialist.

ChanningLua/prax-agent · 14 tokens

openclaw-expert

Use this agent when the user has any question about OpenClaw — how it works, how to configure it, how to use specific features, what APIs are available, how agents are structured, or any other OpenClaw-related inquiry. This agent should be used proactively whenever OpenClaw-specific knowledge is needed.\n\n \nContext…

gluk-w/claworc · 510 tokens

qa-test-engineer

This agent ensures test coverage for backend (Go) or frontend (React/TypeScript) code, write new tests, review existing test coverage, or restructure code for testability. This includes after writing new features, fixing bugs, or when preparing for a release.

gluk-w/claworc · 58 tokens

release-manager

Use this agent when you need to manage the full release lifecycle for a feature branch: creating or verifying a PR exists, resolving merge conflicts, waiting for CI to pass, merging to main, and ensuring main branch CI stays green. Examples:\n\n \nContext: The user has finished implementing a feature and wants to get…

gluk-w/claworc · 325 tokens

claworc-dev-troubleshooter

Use this agent when the user reports issues with the local Claworc development environment, encounters unexpected behavior in the control plane backend, frontend, LLM proxy, or running OpenClaw instances, or needs help diagnosing why something isn't working as expected. The agent assumes the environment is already…

gluk-w/claworc · 74 tokens