hashgraph-online/awesome-codex-plugins / plugins/beastlabai/multi-llm-plugin/skills/multi-llm
multi-llm
FlaggedOrchestrate plan reviews, task generation, implementation and code reviews across several LLM CLIs in parallel, or ask every model one free-text question about a plan. Use when the user says: review my plan, multi-llm, run a code review, generate tasks from a plan, implement this plan, ask the models about my plan.
assets/omp/overlay.yml
View on GitHub# multi-llm's per-run overlay for omp. Loaded with --config on every dispatch.
#
# Read at an ABSOLUTE path (utils/providers/omp.py's OVERLAY_PATH): a relative
# --config resolves against omp's --cwd rather than the launch cwd, and a
# missing overlay is a fast, named launch failure (exit 1 in 0.13 s, zero
# requests, `error: Config overlay not found: <path>`) rather than a run that
# silently used omp's own defaults.
retry:
enabled: false # §1.9: omp's default retry never terminates on a 429
# (35 requests in 90 s and still going). Disabled, a
# failing model call ends after the one hard-coded
# layer below this one — the Responses client's 6
# requests, 16 s on a 500 and 100.5 s on a 429 whose
# body names a 20 s delay — which is what classifies
# as `rate_limited` instead of eating the whole slot.
# (12 requests, ~32 s is the completions client, which
# the shipped model specs never dispatch on — see
# omp.py's `internal_retries`.)
mcp:
enableProjectConfig: false # §1.8/§2.3: MCP tools are appended to the enabled
# set regardless of --tools, so an unfiltered
# mcp__ tool would be an unbounded `yolo`.
# MEASURED 2026-09-17 at 18.2.2 (P5): with a
# populated .cursor/mcp.json in the spawn cwd the
# project server process starts without this key
# and does NOT start with it. The user-level
# ~/.cursor/mcp.json never mounted on an ordinary
# dispatch — not from a repo cwd and not with
# --cwd $HOME — because that mount needs
# --allow-home, which this adapter never renders.
# Off by decision (§2.9): this repo's AGENTS.md / CLAUDE.md are read by every
# omp dispatch — --no-rules does not stop it, because they are the
# `context-files` category, not `rules` (§1.8). Uncomment to keep the repo's
# conventions out of your reviewers:
# disabledExtensions:
# - context-file:project:AGENTS.md
# - context-file:project:CLAUDE.md
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |