lac5q
UserBeastmode: MofA (Mixture of Agents) orchestration framework for Hermes/OpenClaw/Codex with MemroOS-style context continuity.
Categories
Indexed Skills (16)
beastmode
Multi-agent orchestration framework for high-intensity feature implementation. Routes work across model tiers: frontier models (Claude Fable, Kimi 3, Opus; Codex only when explicitly selected) own design, architecture, and review sign-off, while economy models (MiniMax M3, Qwen/Gwen) handle implementation and mechanical validation in isolated worktrees, with a self-improving learning loop that promotes lessons back into skills. Harness-agnostic: works with Hermes ACN (async parallel sub-agents), Pi, Claude Code, Codex, Ultraswarm, GSD, delegate_task, or manual orchestration.
beastmode-claude-code
Claude Code harness adapter for the universal Beastmode MofA framework
beastmode-codex
Codex harness adapter for the universal Beastmode MofA framework, absorbing the beastmode-cloud worker lanes
beastmode-hermes
Hermes harness adapter for the universal Beastmode MofA framework - ACN async parallel sub-agents via delegate_task. Use when Luis asks for beastmode, Mixture-of-Agents, autonomous goal execution, or a phase takeover inside a Hermes session.
beastmode-pi
Pi-specific harness adapter for the universal Beastmode MofA orchestration framework (see the `beastmode` skill, v2.1). Composes five installed pi packages into the universal loop — pi-goal as the in-session goal engine, pi-dynamic-workflows as the fan-out / model-router, pi-loop-police as the anti-spin circuit breaker, pi-permission-system as the worker-contract enforcer, rpiv-todo + pi-telegram as live visibility. Use when Luis asks for beastmode, a Mixture-of-Agents run, autonomous goal execution, planner/worker/watcher, or a phase takeover inside a pi session.
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
gitnexus-exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
gitnexus-guide
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
memroos-save
Persist durable agent work product to MemroOS MCP knowledge base with verification, metadata, and source-drift support. Use when producing research, competitive analysis, market positioning, comparison posts, benchmarks, RCA documents, or any "save/document/archive" request. Auto-validates the write succeeded.
beastmode-cloud
Run Codex- or Cursor-led Beastmode with pluggable external workers such as Qwen, direct MiniMax API, Droid MiniMax, GLM, or other Droid models.
beastmode-qwen-cloud
Backward-compatible Beastmode entrypoint. Prefer beastmode-cloud for pluggable Qwen, Droid MiniMax, GLM, and other model workers.
qwen-cloud
Delegate a bounded Codex Cloud task to the Qwen executor CLI installed by scripts/setup-codex-cloud.sh.
goal
Create or resume a MemRoOS /goal work session with acceptance criteria, lane selection, context packet, and proof requirements.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.