Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Safe Exec
v0.3.4Safe command execution for OpenClaw Agents with automatic danger pattern detection, risk assessment, user approval workflow, and audit logging. Use when agen...
⭐ 8· 7.8k·108 current·120 all-time
by@ottttto
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's stated purpose (intercept dangerous shell commands and provide an approval workflow) matches the included bash scripts and audit-log behavior. However the documentation asserts "automatically monitors all shell command executions" and "runs transparently in the background" while also declaring "No background monitoring processes" — the package appears to be a wrapper that requires routing commands through it (e.g., via agent configuration or symlinks), not a system-wide interceptor. There is also a small metadata mismatch: SKILL.md declares a dependency on jq and a git install step, but the top-level registry metadata lists none; this inconsistency should be clarified.
Instruction Scope
SKILL.md and READMEs repeatedly claim full session/command monitoring and in-session prompts but the shipped code is a set of wrapper/utility scripts (safe-exec.sh, approve/list/reject, AI wrapper). There is no visible code that would transparently hook every shell invocation system-wide; instead the agent or user must route commands through safe-exec. That difference (wrapper vs global monitor) is material and under-documented. Additionally, agent-mode behavior (non-interactive auto-bypass) is documented but grants automated flows the ability to execute commands with less human friction — this is within the skill's purpose but expands what will run automatically.
Install Mechanism
No high-risk installers (archive downloads or shorteners) are used; SKILL.md recommends cloning from GitHub (https://github.com/OTTTTTO/safe-exec.git). The package included in the registry contains the scripts and docs. The install flow is git-based and transparent, which is reasonable, but the registry listing lacks the same install metadata so the install guidance in SKILL.md should be treated as authoritative only after verifying the repository source.
Credentials
The skill declares only local control env vars (SAFE_EXEC_DISABLE, OPENCLAW_AGENT_CALL, SAFE_EXEC_AUTO_CONFIRM) and writes to ~/.openclaw/safe-exec/ and an audit log — no external credentials or network access. That is proportional. However SAFE_EXEC_AUTO_CONFIRM and OPENCLAW_AGENT_CALL are explicit switches that allow non-interactive approvals; if set or used by an agent, LOW/MEDIUM commands (and in some flows approvals) may be auto-executed without human confirmation. If you enable these env vars or allow agents to set them, the blast radius increases.
Persistence & Privilege
The skill is not 'always:true' and doesn't request elevated platform privileges, and it persists data under the user home (~/.openclaw). However there is ambiguous language about running 'in the background' vs 'no background processes'. The included files show a pending queue and logs (persistent files), but no cron/daemon scripts in the provided files. Before trusting it, verify the main entrypoint safe-exec.sh for any modifications to shell startup files (e.g., .bashrc) or installation steps that alter PATH or create persistent hooks.
What to consider before installing
What to check before installing:
- Verify the git repository (https://github.com/OTTTTTO/safe-exec.git) content and commit history yourself rather than relying solely on the SKILL.md claims.
- Inspect the main script (~/.openclaw/skills/safe-exec/safe-exec.sh) to confirm how it intercepts commands: is it a wrapper that agents must call, or does it install shell hooks or modify startup files? Look for any edits to ~/.bashrc, ~/.profile, /etc files, or creation of daemons.
- Understand agent-mode auto-approval: avoid setting SAFE_EXEC_AUTO_CONFIRM or exposing OPENCLAW_AGENT_CALL to untrusted agents. If you need automation, restrict which agents can set these vars and review the audit log frequently.
- Ensure jq (declared dependency) is installed and that the git source is what you expect; the registry metadata and SKILL.md differ on declared requirements—clarify this discrepancy with the author or maintainer.
- Test in an isolated or VM environment first (try harmless commands and known dangerous patterns) to confirm behaviour and that audit logs are generated and complete.
- If you need a true system-wide interceptor rather than a wrapper, do not assume this skill provides that; ask the maintainer for explicit technical details about how global monitoring (if any) is implemented.
Given the inconsistencies and the potential for agents to auto-execute commands via auto-confirm switches, treat this package with caution and validate the exact runtime behavior before enabling it in production or on important systems.Like a lobster shell, security has layers — review code before you run it.
audit-logvk974a9fzv2bsj44fdq36f901zs80b2p8command-executionvk974a9fzv2bsj44fdq36f901zs80b2p8latestvk97fdp888hv9cb4zsb2gngc9px81zrr2risk-assessmentvk974a9fzv2bsj44fdq36f901zs80b2p8securityvk97f3xgxdxrcmr575k37fcm3th81wz4p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Environment variables
SAFE_EXEC_DISABLErequiredOPENCLAW_AGENT_CALLrequiredSAFE_EXEC_AUTO_CONFIRMrequired