T09 · Insecure Skill Coding Practices
- Location
SKILL.md:129- Finding
SQL Injection Through Unvalidated Database Identifiers
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is coherent and purpose-aligned, but users should review generated database SQL before running it.
Install only if you are comfortable granting file access for project data workflows. Treat generated SQL as draft output: validate table, column, and relationship names, review it manually, and run it only in an appropriate database environment with limited privileges.
SKILL.md:129SQL Injection Through Unvalidated Database Identifiers
The instructions broaden the skill from its declared purpose of data-model design into generic document/report generation and analytics, which increases the chance the agent will perform actions outside its intended scope. This kind of scope drift can bypass least-privilege expectations, cause unsafe handling of arbitrary files or data sources, and create ambiguity about what methods from other skill files may be invoked.
The file says to only use user-provided or referenced data, but it also tells the agent to process data using methods described in SKILL.md without clearly constraining what those methods may do. That ambiguity can let less-visible instructions or code in SKILL.md expand behavior, access unintended resources, or override the apparent data-use limitation.
No suspicious patterns detected.