T09 · Insecure Skill Coding Practices
- Location
scripts/script.sh:382- Finding
AWK Command Injection Through the Summarization Ratio
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a mostly coherent local NLP tool, but one summarization option can be abused to run arbitrary shell commands.
Review before installing. Use this only in a constrained environment or after the --ratio handling is fixed to validate numeric input and pass it to AWK as data. Do not feed confidential or regulated documents unless local processing is approved, and treat --json output as untrusted until proper escaping is implemented.
scripts/script.sh:382AWK Command Injection Through the Summarization Ratio
scripts/script.sh:285Unescaped User-Controlled Data Produces Invalid or Manipulated JSON
The code substantially matches the declared NLP purpose for tokenizing, sentiment, extraction, summarization, and similarity. However, it also exposes an additional command, 'classify', which performs text classification and is not mentioned in the declared description. That is an undeclared capability under the evaluation criteria. Additionally, the script can read from local files via --file/--file1/--file2, while declared permissions are empty; this is a resource access inconsistency if permissions are expected to enumerate file access. The primary purpose remains NLP, so this is not a wholly different skill, but the description is not fully accurate.
The extract command explicitly pulls out emails, URLs, dates, numbers, and capitalized names from arbitrary user-supplied text, which can include personal or sensitive data. In an agent skill context, this increases privacy risk because the tool encourages structured extraction of PII without any consent notice, minimization controls, or guidance on safe handling, making downstream misuse or overcollection more likely.
This skill is designed to process arbitrary user text from files and stdin, including emails, reports, and articles, yet it provides no privacy warning about handling sensitive content. While the skill claims to be stateless and local, users may still unintentionally pass confidential data, creating avoidable privacy and compliance risk through insufficient disclosure.
No suspicious patterns detected.