T09 · Insecure Skill Coding Practices
- Location
scripts/validate.py:113- Finding
Configuration Validation Failure Is Ignored by the Final Exit Status
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a straightforward Spring Boot guidance skill with minor documentation and validation-quality issues, but no hidden or unsafe agent behavior.
Install only if you want a broad Spring Boot coding helper that can read, write, and run shell commands in your project. Review generated security code before use, especially CSRF settings, and treat the included validator as a convenience check rather than a strict release gate.
scripts/validate.py:113Configuration Validation Failure Is Ignored by the Final Exit Status
The declared purpose is about Spring Boot application development capabilities, but the supplied code does not implement or support Spring Boot app building features such as REST APIs, security, data access, or actuator setup. Instead, it performs repository/skill validation tasks: checking for SKILL.md, required directories, and config.yaml contents. This is a materially different primary purpose from the description, so it should be flagged as a mismatch.
The skill provides a Spring Security example that disables CSRF globally without explaining that this is only appropriate for strictly stateless, non-browser-based APIs. Users may copy this configuration into cookie-based or browser-accessible applications, which can expose state-changing endpoints to cross-site request forgery attacks.
This markdown file documents how to invoke the skill, so SQP-1 applies. The pattern claude "java-spring-boot - [your task description]" shows a broad free-form trigger format but does not define boundaries, exclusions, or negative examples, making it unclear what requests should or should not activate the skill.
No suspicious patterns detected.