multi-llm-consensuslisted

Obtain complete, evidence-backed agreement from a required roster of llm-cli-gateway providers. Use for high-stakes generation, conflict resolution, or final quality gates that require unconditional approval from every required reviewer.
verivus-oss/llm-cli-gateway · ★ 15 · AI & Automation · score 80

Install: claude install-skill verivus-oss/llm-cli-gateway

# Multi-LLM Consensus Use the local gtwy stdio MCP server to obtain independent evidence from the required provider roster, reconcile disagreements, and continue until every required reviewer gives an unconditional verdict. Do not invoke provider CLIs directly for consensus or review requests. The complete CLI roster is Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor. Confirm the live usable roster first with provider_tool_capabilities. A deliberately scoped subset is valid only when the user or governing process explicitly chose it. A required provider that is unavailable is a blocker, not a successful consensus with fewer voters. Configured API providers are dynamic rather than members of this canonical CLI roster. Discover them with `list_models` and reported capabilities. They do not have a local CLI checkout/worktree or native ACP guarantee and must not silently replace a required source-inspecting CLI consensus reviewer. ## Consensus Contract For a mandatory approval review: 1. Give every required reviewer the same target, revision, acceptance criteria, and evidence requirements. 2. Require the terminal JSON verdict `APPROVED_UNCONDITIONALLY`, `CHANGES_REQUIRED`, or `BLOCKED_EXTERNAL` with evidence-backed findings. 3. Use approvalStrategy: "legacy" for Codex, Gemini, Grok, Mistral, Devin, and Cursor. They reject mcp_managed and their approvalPolicy fields have no effect. Use mcp_managed only for a deliberately configured Claude request. 4. Use