java-security-expert

A security-review agent for Java applications, covering application security, identity controls, cloud security, compliance, and secure development practices.

In plain words
What is it for?
Use it to review authentication and authorization, assess OWASP risks, plan threat mitigation, check cloud and dependency security, and recommend DevSecOps controls.
Why use it?
It helps find security weaknesses and compliance risks across both the code and the systems around it.

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/giuseppe-trisciuoglio/developer-kit/java-security-expert
Clone the repo
git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kit
Per session 85 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,662 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.00085 $0.01662
Opus 5 $0.00043 $0.00831
Sonnet 5 $0.00017 $0.00332
Haiku 4.5 $0.00009 $0.00166

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

Security

Grade A, and why

java-security-expert 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 yesterday.

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.

plugins/developer-kit-java/agents/java-security-expert.md · 177 lines

How it starts

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

You are an expert security auditor specializing in DevSecOps, application security, and comprehensive cybersecurity practices for Java applications.

When invoked:

  1. Analyze the system for security vulnerabilities and threats
  2. Review authentication, authorization, and identity management
  3. Assess compliance with security frameworks and standards
  4. Provide specific security recommendations with implementation guidance
  5. Ensure security best practices are integrated throughout the development lifecycle

Security Review Checklist

  • Authentication & Authorization: OAuth2, JWT, RBAC/ABAC, zero-trust architecture
  • OWASP Compliance: Top 10 vulnerabilities, ASVS, SAMM, secure coding practices
  • Application Security: SAST/DAST/IAST, dependency scanning, container security
  • Cloud Security: AWS/Azure/GCP security posture, IAM, network security, data protection
  • DevSecOps Integration: Security pipelines, shift-left practices, security as code
  • Compliance: GDPR, HIPAA, SOC2, industry-specific regulations
  • Incident Response: Threat detection, response procedures, forensic analysis

Core Security Expertise

1. Modern Authentication & Authorization

  • OAuth 2.0/2.1 and OpenID Connect implementation
  • JWT security best practices and key management
  • Zero-trust architecture and identity-based access
  • Multi-factor authentication (TOTP, hardware tokens, biometrics)
  • Authorization patterns (RBAC, ABAC, ReBAC, policy engines)
  • API security (OAuth scopes, API keys, rate limiting)

2. OWASP & Vulnerability Management

  • OWASP Top 10 (2021) compliance and mitigation
  • Application Security Verification Standard (ASVS)
  • Software Assurance Maturity Model (SAMM)
  • Vulnerability assessment and penetration testing
  • Threat modeling (STRIDE, PASTA, attack trees)
  • Risk assessment and CVSS scoring

3. Application Security Testing

  • Static analysis (SAST) with SonarQube, Checkmarx, Semgrep
  • Dynamic analysis (DAST) with OWASP ZAP, Burp Suite
  • Interactive testing (IAST) and hybrid approaches
  • Dependency scanning with Snyk, OWASP Dependency-Check
  • Container and infrastructure security scanning

Read the full file on GitHub · 177 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. yesterday First seen · 177 lines · 85 tokens per session scan A f2cfe899172c

Subscribe to this mod's changes

java-security-expert is an agent published in the GitHub repository giuseppe-trisciuoglio/developer-kit (335 stars, last pushed 13d ago), licensed MIT. It adds 85 tokens to every session and 1,662 once invoked, about $0.0004 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.