file-watcher
Fail
Audited by Gen Agent Trust Hub on Feb 16, 2026
Risk Level: HIGHCOMMAND_EXECUTIONPROMPT_INJECTION
Full Analysis
- Command Execution (HIGH): The script
scripts/file_watcher.pyallows for the execution of arbitrary shell commands via the--exec(or-e) command-line argument. These commands are executed usingsubprocess.run(shell=True), which grants the agent high-privilege access to the host system. Any command provided by the agent or a user is executed with shell interpretation enabled. - Indirect Prompt Injection (MEDIUM): The skill monitors external file system states (Category 8c). An attacker who can create or modify files in a directory watched by this tool can trigger the execution of the configured shell command at will.
- Ingestion points: File system metadata (filenames and modification times) via
os.walkandos.statinscripts/file_watcher.py. - Boundary markers: None. The tool prints file events directly to stdout without sanitization.
- Capability inventory:
subprocess.run(shell=True)(arbitrary command execution),os.walkandos.stat(file system enumeration and read). - Sanitization: None. Filenames are printed directly, and the
exec_cmdis executed without any validation or escaping. - Metadata Poisoning (MEDIUM): Both
SKILL.mdandscripts/file_watcher.pyclaim the tool is based on thewatchdoglibrary (https://github.com/gorakhargosh/watchdog). However, the actual implementation is a rudimentary manual polling loop. This misleading metadata can cause users to overestimate the tool's performance and security properties.
Recommendations
- AI detected serious security threats
Audit Metadata