Java secure coding

Skill andresnator/agents-orchestrator/skills/java-secure-coding

Trigger: Java secure coding, Oracle Secure Coding Guidelines, input validation, trust boundaries, deserialization, least privilege, sensitive data. Review Java code for secure implementation practices.From its SKILL.md

Install

npx -y skills add andresnator/agents-orchestrator --skill java-secure-coding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.1 KB, 567 tokens by cl100k_base, as published. Nobody here has run it

Skill: java-secure-coding

Activation Contract

Use this skill when reviewing or designing Java code for secure coding practices: input validation, trust boundaries, injection, serialization/deserialization, sensitive data, resource exhaustion, mutability, access control, and third-party code risk.

Do not use this skill for full threat modeling, compliance audits, cryptography design, infrastructure hardening, or non-Java security work.

Responsibility

This skill teaches Java secure-coding review based on Java platform concerns and Oracle Secure Coding Guidelines. It does not call other skills, certify security, or replace a formal security review.

Required Context

Data sources and trust boundaries.
Inputs accepted and outputs generated.
Sensitive data handled.
Resource-intensive operations.
Serialization, reflection, XML, SQL, command execution, or third-party dependencies involved.

Context Budget

Keep this SKILL.md focused on secure-coding decisions.
Use references/java-secure-coding-guidance.md for checklist details.

Hard Rules

Establish trust boundaries before judging input safety.
Validate and canonicalize untrusted input before use.
Avoid dynamic SQL; use parameterized statements or safe higher-level APIs.
Do not log secrets or expose sensitive data in exceptions.
Release resources and defend against resource exhaustion.
Treat deserialization, XML, reflection, JNDI, command execution, and third-party code as high-risk areas.
Prefer least privilege and minimal accessibility.

Decision Gates

Condition	Action
Untrusted input crosses boundary	Validate type, range, size, format, and canonical form.
SQL uses string concatenation	Replace with parameterized query shape.
XML or deserialization is involved	Require restrictive parser/filter configuration.
Sensitive data appears in logs/exceptions	Remove, redact, or sanitize.
Resource size depends on input	Add limits and overflow-safe checks.
Public/extensible surface exposes internals	Reduce accessibility or document/guard contract.

Execution Steps

Identify trust boundaries and untrusted data.
Check injection, inclusion, deserialization, and resource risks.
Check sensitive-data exposure.
Check mutability, access, and privilege boundaries.
Return findings with severity and remediation.

Output Contract

Return:

Secure-coding verdict: low_risk, needs_hardening, or high_risk.
Findings with severity and evidence.
Recommended remediation.
Residual risks and assumptions.
Areas requiring formal security review, if any.

References

references/java-secure-coding-guidance.md — Java secure-coding checklist based on official guidance themes.

Assets

None.

What ships with it: 1 file

1.6 KB alongside SKILL.md

references/

java-secure-coding-guidance.md1.6 KB

Gives 0 of the 12 instructions most security skills give in 567 tokens

Counted across 648 of the 828 authors here whose files we hold, read 2026-08-07

Parameterize all database queriesin 68 of 648, across 51 files
Hash passwords using bcrypt, scrypt, or argon2in 49 of 648, across 36 files
Apply rate limiting to authentication endpointsin 48 of 648, across 24 files
Configure security headersin 35 of 648, across 19 files
Validate all inputsin 32 of 648, across 24 files
Validate all external input at the system boundaryin 29 of 648, across 19 files
Run containers as a non-root userin 28 of 648, across 15 files
Use httponly secure samesite cookies for sessionsin 26 of 648, across 15 files
Run dependency audits before every releasein 21 of 648, across 10 files
Encode output to prevent cross-site scriptingin 21 of 648, across 11 files
Copy dependencies before source codein 20 of 648, across 9 files
Store secrets in environment variablesin 20 of 648, across 18 files

Said here and by no other author read

Establish trust boundaries before judging input safety
Validate and canonicalize untrusted input before use
Avoid dynamic SQL
Do not log secrets
Release resources and defend against resource exhaustion
Treat deserialization as high-risk

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.