← ClaudeAtlas

beastmode-qwen-cloudlisted

Backward-compatible Beastmode entrypoint. Prefer beastmode-cloud for pluggable Qwen, Droid MiniMax, GLM, and other model workers.
lac5q/memroos · ★ 6 · AI & Automation · score 61
Install: claude install-skill lac5q/memroos
# Beastmode Qwen Cloud Use this skill when Luis asks for Beastmode, Qwen, cheap-worker execution, or a planner/worker/validator pattern inside Codex Cloud. This is the legacy Qwen-specific entrypoint. For new Beastmode runs, prefer `$beastmode-cloud`, which supports Qwen plus Droid models such as `minimax-m3`, GLM, and other configured Factory models. Codex Cloud does not make Qwen a native Codex model. This skill implements one worker lane by using Qwen as an external executor CLI: - Director: Codex in the current session. - Worker: `~/.local/bin/qwen-agent` using `qwen3.7-plus`. - Validator: Codex in the current session, plus repo tests/checks. ## Start Gate Confirm the Qwen lane is real before using it for work: ```bash ~/.local/bin/qwen-agent --dangerously-skip-permissions -p "Reply with exactly: QWEN OK" ``` If this fails because `DASHSCOPE_API_KEY` is missing, continue as Codex-only and report that Beastmode is statically installed but the Qwen worker is not live-verified. ## Operating Loop 1. Codex writes the plan, scope, acceptance checks, and blast-radius notes. 2. Codex delegates only a bounded executor slice to Qwen. 3. Qwen returns a patch, findings, or an implementation transcript. 4. Codex reviews all output, applies only acceptable changes, and runs checks. 5. Codex records what actually happened: installed, delegated, verified, or blocked. ## Qwen Worker Contract Every Qwen prompt must include: - The exact repo path and task objective. - Allowe