T09 · Insecure Skill Coding Practices
- Location
SKILL.md:112- Finding
Shell Command Injection Through Unsafe Placeholder Interpolation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill has a coherent todo-to-Google workflow, but its documented shell commands use unsafe interpolation for task data and file paths, creating a real review-worthy command-injection risk.
Review this skill before installing. Its core behavior is understandable, but only use it with trusted todo content and file paths, and prefer an implementation that calls gog with structured arguments rather than assembled shell strings. Be aware that syncing or archiving sends selected todo/work-log data to Google services.
SKILL.md:112Shell Command Injection Through Unsafe Placeholder Interpolation
The skill explicitly syncs local todo content and work logs to Google Tasks and uploads files to Google Drive, but it does not warn the user that task titles, notes, dates, and archived files will be transmitted to external cloud services. This creates a real privacy and data-handling risk because users may unknowingly expose sensitive work information outside the local environment.
The archive function uploads a local todo file to Google Drive and converts it to a Google Doc, but it lacks an explicit privacy or data-transfer warning. Because todo files may contain work logs, summaries, deadlines, and notes, this can expose sensitive operational or personal information to a third-party cloud platform if the user does not fully understand the transfer.
The skill automatically creates and modifies local markdown todo files as part of normal operation, but it does not clearly warn the user about filesystem changes. While this is expected for a todo manager, silent file creation and editing can still surprise users, overwrite expected content structure, or persist sensitive information locally without informed consent.