beastmode-cloudlisted

# Beastmode Cloud Use this skill when Luis asks for Beastmode, cheap-worker execution, planner/worker/validator loops, Qwen, MiniMax, Droid, or multi-model coding support in a cloud coding session. The current agent stays the director, reviewer, and merge gate. External models are bounded workers only. Never let a worker commit, push, access secrets, or claim final verification. ## Worker Lanes Choose the lane that is installed and authenticated on the host: | Lane | Default model | Command | Smoke gate | |------|---------------|---------|------------| | Qwen | `qwen3.7-plus` | `~/.local/bin/qwen-agent` | Must return `QWEN OK` | | MiniMax API | `MiniMax-M3` | `curl https://api.minimax.io/v1/chat/completions` | Must return `MINIMAX OK` | | Droid MiniMax | `minimax-m3` | `~/.local/bin/droid exec --model minimax-m3` | `droid exec --model minimax-m3 "Reply with exactly: MINIMAX OK"` | | Droid custom | any `droid exec --list-tools` model id | `~/.local/bin/droid exec --model <id>` | Model-specific exact reply | Prefer the direct MiniMax API lane when `MINIMAX_API_KEY` is present and the worker only needs to return a patch, plan, or analysis. Use Droid MiniMax when you specifically need Factory's agent runtime or tool access. Prefer an independent validator model when the authoring worker was MiniMax. ## Start Gate **Check 1Password before declaring a lane unavailable.** `$MINIMAX_API_KEY` is often unset in the shell even when the key exists — it lives in 1Password, not the