Skip to main content
skill CX Codex

124-java-secure-coding — Claude Code skill: Java security

124-java-secure-coding is a Claude Code skill that reviews Java code for security flaws. It runs on requests to check input handling, injection risks, or error handling.

Apache-2.0 491 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 124-java-secure-coding -a claude-code
Open on GitHub

What 124-java-secure-coding does

The skill checks Java code for risks involving untrusted input, injection, cryptography, secrets, deserialization, and XSS. Its reference file gives good and bad code examples, which the agent uses to choose protections relevant to the project.

Before editing, the agent runs ./mvnw compile or mvn compile; it stops if compilation fails. After changes, it runs ./mvnw clean verify or mvn clean verify. Detailed examples and constraints are in references/124-java-secure-coding.md.

What it helps with

  • find Java input-validation risks
  • detect SQL, OS, and LDAP injection flaws
  • review exception handling for sensitive-data leaks
  • harden Java code against unsafe deserialization and XSS

Example prompts for the agent

  • Review this Java code for secure-coding vulnerabilities.
  • Find input-validation and injection risks in the Java code.
  • Improve error handling in this Java service without exposing sensitive data.

How to install 124-java-secure-coding

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 124-java-secure-coding -a claude-code

2Manually: put the files in place

~/.claude/skills/124-java-secure-coding/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/124-java-secure-coding/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 124-java-secure-coding

How do I install 124-java-secure-coding in Claude Code?

Run npx skills add jabrena/plinth --skill 124-java-secure-coding -a claude-code. The skill file is at ~/.claude/skills/124-java-secure-coding/SKILL.md.

What does 124-java-secure-coding do?

It helps identify Java security flaws and apply protections for input, queries, secrets, cryptography, deserialization, and output.

Which build commands does 124-java-secure-coding run?

Before edits, it runs ./mvnw compile or mvn compile and stops if compilation fails. After changes, it runs ./mvnw clean verify or mvn clean verify.

Source text

SKILL.md · Apache-2.0
---
name: 124-java-secure-coding
description: Use when you need to apply Java secure coding best practices — including validating untrusted inputs, defending against injection attacks with parameterized queries, minimizing attack surface via least privilege, applying strong cryptographic algorithms, handling exceptions securely without exposing sensitive data, managing secrets at runtime, avoiding unsafe deserialization, and encoding output to prevent XSS. This should trigger for requests such as Review Java code for secure coding; Find input validation risks in Java code; Review Java code for injection vulnerabilities; Improve secure error handling in Java services; Harden Java code against common security flaws. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# Java Secure coding guidelines

Identify and apply Java secure coding practices to reduce vulnerabilities, protect sensitive data, and harden application behaviour against common attack vectors.

**What is covered in this Skill?**

- Input validation: type, length, format, and range checks
- SQL/OS/LDAP injection defence via `PreparedStatement` and parameterized APIs
- Attack surface minimisation: least-privilege permissions, removal of unused features
- Strong cryptography: BCrypt/Argon2 for passwords, AES-GCM for encryption, digital signatures; avoid deprecated ciphers (MD5, SHA-1, DES)
- Secure exception handling: log diagnostic details internally, expose only generic messages to clients
- Secrets management: load credentials from environment variables or secret managers — never hardcoded
- Safe deserialization: strict allow-lists, prefer explicit DTOs over native Java serialization
- Output encoding to prevent XSS in rendered content

**Scope:** The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples.

## Constraints

Before applying any secure coding changes, ensure the project compiles. If compilation fails, stop immediately — do not proceed until resolved. After applying improvements, run full verification.

- **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any changes
- **SAFETY**: If compilation fails, stop immediately — do not proceed until the project is in a valid state
- **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements
- **BEFORE APPLYING**: Read the reference for detailed good/bad examples, constraints, and safeguards for each secure coding pattern

## When to use this skill

- Review Java code for secure coding
- Find input validation risks in Java code
- Review Java code for injection vulnerabilities
- Improve secure error handling in Java services
- Harden Java code against common security flaws

## Workflow

1. **Compile project before secure-coding changes**

Run `./mvnw compile` or `mvn compile` and stop immediately if compilation fails.

2. **Read secure-coding reference and assess risks**

Read `references/124-java-secure-coding.md` and identify applicable vulnerabilities and hardening opportunities.

3. **Apply secure-coding improvements**

Implement selected protections for input validation, crypto, secrets, deserialization, and output encoding.

4. **Verify with full build**

Run `./mvnw clean verify` or `mvn clean verify` after applying improvements.

## Reference

For detailed guidance, examples, and constraints, see [references/124-java-secure-coding.md](references/124-java-secure-coding.md).

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Security →

From the same set123

The whole set →
110-java-maven-best-practices 110-java-maven-best-practices is a skill that reviews and rewrites Maven configuration using industry practices, including BOM-based dependency management, centralized versions, and multi-module builds. CX Codex +1 512installs 121-java-object-oriented-design 121-java-object-oriented-design reviews Java code against SOLID, DRY and YAGNI, flags God Class and Feature Envy, and applies small refactorings. Useful when reworking an object model. CX Codex +1 505installs 131-java-testing-unit-testing 131-java-testing-unit-testing is a Claude Code skill that reviews and improves Java unit tests with JUnit 5, AssertJ, and Mockito, catching anti-patterns and checking boundary conditions. CX Codex +1 479installs 141-java-refactoring-with-modern-features 141-java-refactoring-with-modern-features — a skill that moves legacy Java code onto modern language features: lambdas, Stream API, Optional, java.time. Useful when a codebase needs cleanup. CX Codex +1 459installs 125-java-concurrency 125-java-concurrency — a skill that has your coding agent review Java code for race conditions, lock contention and thread leaks, then apply modern java.util.concurrent fixes. CX Codex +1 432installs 301-frameworks-spring-boot-core 301-frameworks-spring-boot-core enforces constructor injection and fail-fast config validation in Spring Boot 4.0.x codebases with strict Maven verification. CX Codex +1 421installs 302-frameworks-spring-boot-rest 302-frameworks-spring-boot-rest — a skill that guides an agent through designing and reviewing Spring Boot REST APIs: methods, status codes, DTOs, versioning, pagination, RFC 7807 errors. CX Codex +1 420installs 122-java-type-design 122-java-type-design — a skill that reviews and refactors Java code for type design: kills primitive obsession, builds type hierarchies, picks BigDecimal where precision matters. CX Codex +1 418installs

Project sponsors

Companies that keep this analytics open