Security audit
Security checks for vulnerabilities and agentic risk
The skill is mainly Java coding guidance, but it asks for broad read/write/command authority and describes callbacks, API use, and automation beyond that stated purpose.
Review this skill before installing. Its Java guidance is ordinary, but its declared authority and documentation are broader than a Java robustness helper needs. Only install it if you are comfortable granting read/write/exec capability and possible API or callback use, and require explicit approval before it modifies files, runs commands, or sends data outside the workspace.
The skill is advertised as narrowly focused Java robustness guidance, but the later documentation expands it into generic file processing, API integration, and command execution. This capability mismatch increases the chance the agent will invoke a higher-privilege skill for requests that appear low-risk, enabling unnecessary write/exec/network actions beyond user expectations.
A callback URL and external API/network-oriented behavior are not justified by a Java robustness coding assistant and introduce unnecessary outbound communication paths. In an agent context, this can enable data exfiltration, SSRF-style access to internal endpoints, or silent transmission of code and metadata to third parties.
The documentation frames the skill as Java robustness help but later describes a broad automation tool capable of files, APIs, commands, and data pipelines. This hidden breadth is dangerous because users and orchestrators may grant trust based on the narrow label while the skill can perform materially more sensitive operations.
The activation wording is broad enough to match generic coding, debugging, deployment, and development requests, which can cause over-selection of a skill that has read/write/exec capabilities. Over-broad routing increases the likelihood of this skill being invoked in contexts where those powerful tools are unnecessary, raising the attack surface.
The markdown advertises file writing, external API use, and command execution without prominent warnings or consent requirements for these impactful actions. In an agent system, that omission can normalize dangerous behavior and permit destructive filesystem changes, data leakage over the network, or shell command abuse under the guise of a benign programming helper.
No suspicious patterns detected.
