Back to skill

Security audit

Workspace Guardian

Security checks for vulnerabilities and agentic risk

Overview

Workspace Guardian is a disclosed file-organization skill, with the main caution that its cleanup rules could delete rejected or temporary outputs if followed too broadly.

Before installing, tell the agent to confirm exact paths before deleting files and to limit cleanup to temporary or rejected files it created during the current task. Use explicit output paths for important projects.

Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Vague Triggers

Medium
Confidence
83% confidence
Finding
The rule 'Unless the user explicitly specifies a path, this skill governs where and how files are created' is broad enough to affect nearly all file-writing behavior without clearly defining scope boundaries. In an agent environment, this can override task-specific expectations and cause files to be written into unexpected managed locations, increasing the risk of misplaced outputs, accidental overwrites, or policy conflicts with other skills.

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The instruction to 'remove the file promptly' when a user declines an output authorizes destructive deletion without an explicit confirmation step or warning at the time of deletion. In practice, a user may reject content quality rather than request destruction, and an agent could delete files the user expected to revise, retain, or audit later.

Missing User Warnings

Medium
Confidence
89% confidence
Finding
Automatic cleanup of temp files after task completion describes deletion behavior but does not require advance user notice, scope limits, or safeguards against deleting files still needed for debugging, recovery, or concurrent work. In shared or loosely structured workspaces, an agent may classify files as temporary too aggressively and remove data unexpectedly.

Static analysis

No suspicious patterns detected.