DCG Guard
Analysis
DCG Guard appears to be a real shell-command safety plugin, but its artifacts include risky install and verification instructions that deserve review before use.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Run this in your agent: exec: rm -rf /home/test
The verification instructions ask the agent/user to run a real recursive delete command. If the plugin is not installed, not registered, or fails open, the command could execute instead of being blocked.
curl -sSL https://raw.githubusercontent.com/Dicklesworthstone/destructive_command_guard/master/install.sh | bash
The installer executes a remote script from a mutable GitHub branch without a pinned commit, checksum, or included copy of the installer.
api.on("before_tool_call", ... if (!SHELL_TOOLS.has(toolName.toLowerCase())) return; ... return { block: true, blockReason: ... }The plugin registers a gateway-level hook that inspects exec/bash calls and can block them. This is the advertised purpose, but it is broad control over shell tool behavior.
Fail-open. If DCG binary is missing or crashes, commands pass through.
The skill is described as hard-blocking dangerous commands, but it also discloses a fail-open mode. Users should not treat it as a complete guarantee that every dangerous command will be stopped.
