moai-ref-cross-model-audit

Converges Claude, Codex, and GLM code review verdicts via the audit_multi MCP tool.

1.2k|222|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/modu-ai/moai-adk --skill moai-ref-cross-model-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-ref-cross-model-audit
Source: https://github.com/modu-ai/moai-adk/tree/main/internal/template/templates/.claude/skills/moai-ref-cross-model-audit
Command: npx skills add https://github.com/modu-ai/moai-adk --skill moai-ref-cross-model-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a project opts into multi-model auditing, a single reviewer's verdict may miss defects that another model would catch. This Skill defines how plan-auditor and sync-auditor agents fan a code review out across the Codex and GLM backends in parallel, converge their verdicts with the in-session Claude verdict, and fold the per-backend results and disagreement flag into the final audit output.

Core Features & Use Cases

  • Single MCP entry point: Documents the mcp__moai__audit_multi tool, its input parameters (claude_verdict, target, focus, gates, session_id, project_root), and its structured ConvergenceResult output.
  • Independence enforcement: Explains the load-bearing rule that secondary backends receive only a scope, focus area, and directory — never Claude's analysis — so their verdicts remain uncorrelated second opinions.
  • Convergence policy: Defines the 4-case table deriving overall_verdict from required/advisory gates, including fail-open behavior when optional backends are inconclusive.
  • Use Case: An auditor reviewing uncommitted changes in a project configured with audit_model: multi calls audit_multi with its Claude verdict, receives pass/fail verdicts from Codex and GLM, and surfaces a residual-risk note when the backends disagree.

Quick Start

With the project configured to audit_model multi, ask the auditor agent to run a cross-model audit of the uncommitted changes and report the converged verdict with any backend disagreements.

Frequently Asked Questions about moai-ref-cross-model-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a multi-model code review with Claude, Codex, and GLM?

Set audit_model to multi in the project configuration, then have the auditor call the mcp__moai__audit_multi MCP tool with the in-session Claude verdict. The tool fans the review out to Codex and GLM in parallel and returns a converged result.

What is the audit_multi MCP tool and what does it return?

audit_multi is a tool exposed by the moai mcp-server that wraps the convergence engine. It returns a ConvergenceResult containing per-backend verdicts, an overall pass/fail verdict, a disagreement flag, a residual risk note, and any fail-open backends.

When should I use multi-model audit instead of a single backend?

Use multi-model audit only when the project's audit_model is set to multi and a cross-backend second opinion is needed before a verdict. Single-backend paths (claude, codex, or glm only) do not load this skill or invoke convergence.

What happens if the Codex or GLM backend is unavailable during an audit?

Missing, unauthenticated, or erroring backends are marked inconclusive and convergence continues over the remaining backends. If all non-Claude backends are inconclusive, the overall verdict fails open to the in-session Claude verdict.

Why can't I pass Claude's full analysis to the secondary review backends?

Secondary backends must remain uncorrelated second opinions; seeing Claude's reasoning collapses their value into a re-sample of the same analysis. The convergence engine only passes them a target, focus area, and project root.

Does a disagreement between review backends block the audit?

No. A disagreement flag is advisory and surfaced as residual risk in the audit report. Only a required-gate backend failure produces an overall fail verdict; advisory-only conflicts keep the verdict at pass.