Tmux Temp

WarnAudited by ClawScan on May 10, 2026.

Overview

The tmux control helper is mostly coherent, but it encourages launching multiple detached coding agents in yolo/full-auto modes without clear approval boundaries.

Install only if you want the agent to control tmux sessions. Avoid the documented yolo/full-auto coding-agent workflows unless you have isolated worktrees and explicitly approve the launch, and clean up detached sessions when finished.

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.

What this means

If followed, the agent could start other coding agents that make project changes or run commands in parallel before the user reviews each action.

Why it was flagged

The skill explicitly encourages launching coding agents through tmux in yolo/full-auto modes, which are high-impact non-interactive modes that may modify files or run commands without stepwise approval.

Skill content
tmux -S "$SOCKET" send-keys -t agent-1 "cd /tmp/project1 && codex --yolo 'Fix bug X'" Enter ... Codex needs `--yolo` or `--full-auto` for non-interactive fixes
Recommendation

Use this only for explicitly approved workspaces, avoid yolo/full-auto modes unless the repo is isolated, and require user confirmation before launching autonomous coding agents.

What this means

Detached sessions may keep running after the visible chat step finishes, consuming resources or continuing work until killed.

Why it was flagged

The skill documents detached tmux sessions and parallel agent sessions. This is expected for tmux orchestration and cleanup commands are provided, but users should understand these processes can continue running in the background.

Skill content
for i in 1 2 3 4 5; do
  tmux -S "$SOCKET" new-session -d -s "agent-$i"
done
Recommendation

Use the isolated socket, monitor sessions with the printed commands, and run the documented cleanup commands when finished.

What this means

Sensitive terminal output could be surfaced into logs or the agent context when waiting for patterns.

Why it was flagged

The helper intentionally captures tmux pane history and can print the last captured lines on timeout. This is purpose-aligned, but terminal panes may contain secrets, tokens, or private command output.

Skill content
pane_text="$(tmux capture-pane -p -J -t "$target" -S "-${lines}" 2>/dev/null || true)" ... printf '%s\n' "$pane_text" >&2
Recommendation

Use the helper only on intended panes, avoid panes containing secrets, and prefer isolated tmux sockets for agent-controlled sessions.

What this means

Users may have less certainty that the package metadata matches the registry entry they intended to install.

Why it was flagged

The packaged `_meta.json` owner/slug differs from the registry metadata shown for this evaluation, which lists a different owner ID and slug `tmux-temp`. This is a provenance inconsistency, though the included code is visible and small.

Skill content
"ownerId": "kn70pywhg0fyz996kpa8xj89s57yhv26", "slug": "tmux"
Recommendation

Verify the publisher and package identity before installing, especially if relying on this skill in sensitive environments.