T09 · Insecure Skill Coding Practices
- Location
references/zsxq-user-nps.md:27- Finding
Shell Command Injection Through User-Controlled NPS Feedback
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill’s purpose is coherent, but its NPS workflow shows unsafe shell-command handling and a mutable global install recommendation that should be reviewed before use.
Review this before installing. Only submit NPS feedback after explicit confirmation, treat profile and footprint JSON as private account data, and avoid running NPS suggestions through shell-constructed commands. Prefer a pinned, reviewed `zsxq-cli` version and direct argument-array execution for user-supplied feedback.
references/zsxq-user-nps.md:27Shell Command Injection Through User-Controlled NPS Feedback
references/zsxq-user-nps.md:66Unpinned Global Installation of a Mutable npm Dependency
The markdown states that the command retrieves the current account's complete profile, including user ID, location, authentication status, and subscription information. This is sensitive personal/account data, but the document provides no warning about privacy implications, handling of the JSON output, or caution when sharing or storing the result.
The activation guidance encourages proactive invocation when a user expresses dissatisfaction, perceived product gaps, or repeated frustration. Because this command performs a write action that submits feedback to an external service, broad trigger language can lead the agent to initiate or steer toward submission without a sufficiently explicit user request, increasing the risk of unintended actions or manipulation of user sentiment into outbound feedback.
No suspicious patterns detected.