T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:24- Finding
Coding Agents Are Launched with Permission and Approval Safeguards Disabled
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This tmux skill is mostly coherent, but it normalizes launching autonomous coding agents with approval safeguards disabled and ships a shell helper with unsafe argument handling.
Install only if you are comfortable with a skill that may steer agents to run detached coding sessions. Avoid the documented bypass/full-auto flags unless you deliberately run inside a tightly scoped sandbox or throwaway worktree, and treat the bundled wait helper as needing numeric input validation before use in any automation path that could receive untrusted arguments.
SKILL.md:24Coding Agents Are Launched with Permission and Approval Safeguards Disabled
scripts/wait-for-text.sh:29Unvalidated Timeout Arguments Permit Bash Arithmetic Expression Injection
The tmux skill’s stated purpose is terminal multiplexing and pane control, but the quickstart explicitly instructs launching a downstream coding agent with a permission-bypassing flag. That expands the skill into enabling unsandboxed autonomous actions without any safety framing, increasing the chance that users or higher-level agents invoke powerful tooling in a way that can modify files or systems without review.
The documentation shows launching claude --dangerously-skip-permissions with no warning that this disables important safety checks and may allow code execution or file modifications without interactive approval. Omitting that warning is dangerous because the example appears in a quickstart section, making unsafe operation look like the recommended default.
The orchestration section goes beyond managing tmux sessions and actively promotes parallel execution of multiple coding agents, including polling for completion and collecting outputs. In context, this skill becomes an automation wrapper for scaling autonomous agent activity, which materially raises the blast radius of mistakes or misuse because multiple sessions can make concurrent changes across worktrees.
The parallel orchestration example uses fully autonomous flags like --full-auto without any caution about potential code changes, command execution, or system impact across multiple sessions. Because the example normalizes running several agents at once, the absence of warnings amplifies operational risk and can lead to broad unintended modifications.
Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.
target=""
pattern=""
grep_flag="-E"
hard_timeout=0
stale_timeout=300
interval=5
lines=1000
No suspicious patterns detected.