freebuff-commanderlisted
Install: claude install-skill stone623101-cloud/commander-skills
# Freebuff Commander
Use Freebuff as an interactive worker backend. Freebuff is not an OpenCode
JSON runner, so use the bundled tmux dispatcher and harvest files; do not
invent `freebuff run`, API keys, or an OpenRouter endpoint.
## Guardrails
- Run `scripts/freebuff_dispatch.py doctor` before starting workers.
- The target model is `deepseek/deepseek-v4-flash`, displayed by Freebuff as
**DeepSeek V4 Flash 07/31**. The matching built-in root agent is
`base2-free-deepseek-flash`.
- Freebuff currently allows only one active CLI session per account. Running a
second CLI can take over the account and interrupt the first session. Keep
workers serial: finish, harvest, and clean up one worker before starting the
next. Multiple visible iTerm2/tmux tabs do not provide concurrency.
- Limited mode documents six one-hour sessions per day. Treat each worker as
one quota-consuming session; default to one worker and never exceed six
workers per day without explicit user approval.
- Ask the user to confirm the model picker when the TUI does not visibly show
DeepSeek V4 Flash 07/31. Never silently fall back to a paid or unknown model.
- Use read-only workers for research/review. Use separate worktrees for code
changes. Never let workers commit, push, deploy, or publish.
- Prompts travel through `tmux send-keys -l`, and cleanup only terminates
sessions recorded in the current run manifest.
- Treat “Freebuff” in the startup banner as insufficient readiness evidence.
Wai