Back to skill

Security audit

my-content-organizer

Security checks for vulnerabilities and agentic risk

Overview

This organizer is not malicious, but it should be reviewed because it can bulk-move local files, including hidden files despite saying they are skipped.

Use this only in a specific directory you intend to reorganize. Review the dry run carefully and do not run the execute step in a home folder, repository, or secrets-bearing directory unless the hidden-file mismatch is fixed and you have a backup or clear recovery plan.

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Intent-Code Divergence

Medium
Confidence
98% confidence
Finding
The documentation claims hidden files are skipped, but the actual move logic uses `find . -maxdepth 1 -type f`, which will include dotfiles in the current directory. This mismatch can cause sensitive files such as `.env`, `.gitignore`, or editor/config files to be silently relocated into category folders, breaking tooling or exposing secrets during later handling.

Vague Triggers

Medium
Confidence
83% confidence
Finding
The activation guidance is broad enough that an agent could invoke this skill for generic cleanup requests without a strong confirmation boundary, even though the skill performs file-moving operations. In context, unintended invocation is risky because the execution step modifies many user files at once and may reorganize a workspace in ways the user did not explicitly approve.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The skill includes commands that perform bulk `mv` operations, but it does not prominently warn that running the execute step will relocate user files and can affect project structure, scripts, and downstream workflows. In this context, the absence of an explicit modification warning increases the chance of accidental destructive use by an agent or user who interprets the skill as a harmless reporting/cleanup aid.

Static analysis

No suspicious patterns detected.