autolisted

Call relay as `${CLAUDE_PLUGIN_ROOT}/bin/relay` (Claude Code substitutes the plugin's absolute path when this skill loads) — not bare `relay`, which often isn't on the Bash tool's non-interactive PATH. Run ONE of these, matching what the user asked for (default to `status` if they only asked what posture you're in): ``` ${CLAUDE_PLUGIN_ROOT}/bin/relay auto on --session "$CLAUDE_CODE_SESSION_ID" ${CLAUDE_PLUGIN_ROOT}/bin/relay auto off --session "$CLAUDE_CODE_SESSION_ID" ${CLAUDE_PLUGIN_ROOT}/bin/relay auto status --session "$CLAUDE_CODE_SESSION_ID" ``` This only works in a lead session (`/relay:mode` first); it exits with an error otherwise. **Then tell the user, in one line, which posture you now hold and what that changes** — the command prints it, but the user needs to hear it from you, because the posture governs *your* behavior from here on. Use the `🚦 [relay]` marker like every other lead message. - **`on`** → you now hold the **autonomous** posture. Your default inverts from *wait* to *proceed* on the routine, in-plan approval beats — sending the obvious next packet, spawning an executor the approved plan already calls for, reviewing a clean report. Read the "Autonomous mode" section of `/relay:mode`'s role text for exactly what this does and does not license, and follow it: it holds the non-negotiable stop-list, and the rule that **every autonomous action is announced along with what you would have asked**. - **`off`** → back to announce-and-wai