beastmode-cloud

name	beastmode-cloud
description	Run Codex- or Cursor-led Beastmode with pluggable external workers such as Qwen, direct MiniMax API, Droid MiniMax, GLM, or other Droid models.

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 environment. Never conclude MiniMax is "not live" from an absent env var alone. Retrieve it first:

op item list --format=json | python3 -c "
import json,sys
for i in json.load(sys.stdin):
    if 'minimax' in i.get('title','').lower():
        print(i['id'], i['title'], i['vault']['name'])
"
# Use the "Minimax Coding Plan API Key" item (AgentWritable or Clawdbot vault),
# NOT "Minimax API Key Audio" — that's a different product/key.
export MINIMAX_API_KEY="$(op item get <item-id> --vault <vault> --fields credential --reveal)"

Never print the retrieved key to stdout, logs, or chat — pipe it straight into an env var or the request that needs it.

Before delegating, prove the selected lane is live:

# Qwen
~/.local/bin/qwen-agent --dangerously-skip-permissions -p "Reply with exactly: QWEN OK"

# Direct MiniMax API
curl -sS https://api.minimax.io/v1/chat/completions \
  -H "Authorization: Bearer $MINIMAX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"MiniMax-M3","thinking":{"type":"disabled"},"messages":[{"role":"user","content":"Reply with exactly: MINIMAX OK"}],"max_completion_tokens":20,"temperature":0}'

# MiniMax through Droid
~/.local/bin/droid exec --model minimax-m3 "Reply with exactly: MINIMAX OK"

If the smoke check fails, continue without that worker and report the lane as installed but not live-verified.

Operating Loop

1. Director writes the plan, scope, allowed files, acceptance checks, and blast-radius notes.
2. Director delegates only a bounded executor slice to one worker lane.
3. Worker returns a patch, findings, or implementation transcript.
4. Director reviews all output, applies only acceptable changes, and runs checks.
5. Director records what actually happened: installed, delegated, verified, or blocked.

Worker Contract

Every worker prompt must include:

• Exact repo path and task objective.
• Allowed files or directories.
• Commands the worker may run.
• Commands the worker must not run: commit, push, delete, publish, send email, access secrets, or change cloud configuration.
• Required output: summary, unified diff or exact files changed, commands run, verification notes, risks/blockers.

Workers should not receive raw private data, broad environment dumps, API keys, production credentials, legal/financial mail, or other sensitive source text.

Standard Qwen Invocation

mkdir -p .codex/beastmode-runs
run_dir=".codex/beastmode-runs/$(date -u +%Y%m%dT%H%M%SZ)-qwen"
mkdir -p "$run_dir"
cat >"$run_dir/prompt.md" <<'EOF'
You are the bounded worker for a director-led Beastmode run.

REPO:
<absolute repo path>

TASK:
<bounded implementation or analysis slice>

ALLOWED FILES:
<paths>

ACCEPTANCE:
<checks>

DO NOT:
- Commit, push, delete, publish, send email, access secrets, or change cloud configuration.
- Modify files outside the allowed set.
- Claim verification you did not run.

OUTPUT:
- Summary.
- Unified diff or exact files changed.
- Commands run and results.
- Risks or blockers.
EOF
~/.local/bin/qwen-agent --dangerously-skip-permissions -p "$(cat "$run_dir/prompt.md")" >"$run_dir/output.md" 2>&1

Standard Direct MiniMax API Invocation

mkdir -p .codex/beastmode-runs
run_dir=".codex/beastmode-runs/$(date -u +%Y%m%dT%H%M%SZ)-minimax-api"
mkdir -p "$run_dir"
cat >"$run_dir/prompt.md" <<'EOF'
You are the bounded MiniMax worker for a director-led Beastmode run.

REPO:
<absolute repo path>

TASK:
<bounded implementation or analysis slice>

ALLOWED FILES:
<paths>

ACCEPTANCE:
<checks>

DO NOT:
- Commit, push, delete, publish, send email, access secrets, or change cloud configuration.
- Modify files outside the allowed set.
- Claim verification you did not run.

OUTPUT:
- Summary.
- Unified diff or exact files changed.
- Commands run and results.
- Risks or blockers.
EOF
node - "$run_dir/prompt.md" "$run_dir/output.md" <<'NODE'
const fs = require("fs");

const [promptPath, outputPath] = process.argv.slice(2);
const apiKey = process.env.MINIMAX_API_KEY;
if (!apiKey) {
  throw new Error("MINIMAX_API_KEY is required for the direct MiniMax API lane.");
}

const prompt = fs.readFileSync(promptPath, "utf8");
const response = await fetch("https://api.minimax.io/v1/chat/completions", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    model: process.env.BEASTMODE_MINIMAX_MODEL || "MiniMax-M3",
    thinking: { type: "disabled" },
    messages: [{ role: "user", content: prompt }],
    temperature: 0,
    max_completion_tokens: 4096,
  }),
});

const body = await response.text();
if (!response.ok) {
  throw new Error(`MiniMax API ${response.status}: ${body.slice(0, 500)}`);
}
const parsed = JSON.parse(body);
fs.writeFileSync(outputPath, `${parsed.choices?.[0]?.message?.content || ""}\n`);
NODE

Direct API workers cannot inspect the worktree or run tools themselves. Ask for patches, plans, or review findings, then have the director apply and verify. Use thinking.type: disabled for exact-output smoke tests and cleaner worker transcripts.

Standard Droid MiniMax Invocation

mkdir -p .codex/beastmode-runs
run_dir=".codex/beastmode-runs/$(date -u +%Y%m%dT%H%M%SZ)-minimax"
mkdir -p "$run_dir"
cat >"$run_dir/prompt.md" <<'EOF'
You are the bounded MiniMax worker for a director-led Beastmode run.

REPO:
<absolute repo path>

TASK:
<bounded implementation or analysis slice>

ALLOWED FILES:
<paths>

ACCEPTANCE:
<checks>

DO NOT:
- Commit, push, delete, publish, send email, access secrets, or change cloud configuration.
- Modify files outside the allowed set.
- Claim verification you did not run.

OUTPUT:
- Summary.
- Unified diff or exact files changed.
- Commands run and results.
- Risks or blockers.
EOF
~/.local/bin/droid exec --auto low --model "${BEASTMODE_DROID_MODEL:-minimax-m3}" -f "$run_dir/prompt.md" >"$run_dir/output.md" 2>&1

Use --auto low for documentation or small code edits. Use read-only Droid mode for analysis. Raise autonomy only when the director explicitly approves the risk and the environment is isolated.

Validator Duties

After any worker returns:

git diff --stat
git diff --check

Then run the relevant test or build command. If the task touches app code, prefer repo scripts (npm run typecheck, npm run lint, npm test -- --run, or narrower checks) over unreviewed ad hoc validation.

Do not present the work as done until the director has inspected the diff and run relevant verification.