moai-ref-cross-model-audit

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

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/jjjh7401/AI-Lighting_Console --skill moai-ref-cross-model-audit-jjjh7401
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-ref-cross-model-audit
Source: https://github.com/jjjh7401/AI-Lighting_Console/tree/main/.claude/skills/moai-ref-cross-model-audit
Command: npx skills add https://github.com/jjjh7401/AI-Lighting_Console --skill moai-ref-cross-model-audit-jjjh7401

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a project opts into multi-model audit (audit_model: multi), auditors need a second opinion from independent backends before reaching a verdict. This Skill documents how to fan a code review out across the codex and GLM (z.ai) backends in parallel, converge their verdicts with the in-session Claude verdict, and fold the per-backend results plus disagreement flag into the audit output. ## Core Features & Use Cases - Single tool surface: Invokes the mcp__moai__audit_multi MCP tool with the synthesized claude_verdict object, target, focus, gates, and session_id parameters. - Independence rule enforcement: Ensures secondary backends receive only (target, focus) so codex and GLM remain uncorrelated super-reviews rather than re-samples of Claude's reasoning. - Convergence policy: Applies a 4-case table deriving overall_verdict from required/advisory gates, with fail-open identity when optional backends are inconclusive. - Use Case: A plan-auditor finishes its Claude review of uncommitted changes with a concurrency focus, calls audit_multi, receives a required split (codex fails, Claude passes), and reports a conservative FAIL naming the failing backend in the residual-risk section. ## Quick Start Ask the auditor to run a multi-model audit of the uncommitted changes with focus on concurrency and fold the convergence result into the audit verdict.

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 across Claude, codex, and GLM?▼

Call the mcp__moai__audit_multi MCP tool with your in-session Claude verdict folded into the claude_verdict object, plus target and focus. The tool fans out to the codex and GLM backends in parallel and returns a ConvergenceResult with per-backend verdicts and an overall verdict.

When should I use cross-model audit convergence instead of single-model review?▼

Use convergence only when the project's audit_model setting is multi. Single-backend paths (claude-only, codex-only, or glm-only) do not load this skill because no second opinion is needed; convergence is exclusively the multi-model concern.

Why must secondary backends not see Claude's analysis text?▼

Codex and GLM act as uncorrelated super-reviews whose value collapses if they see Claude's reasoning. The convergence engine enforces this structurally by sending only target and focus to secondary backends, so focus must carry a short area name, not analysis paragraphs.

What happens if the codex or GLM backend is missing or unauthenticated?▼

The backend returns verdict inconclusive in its per-backend slot and convergence continues over the remaining active backends. If all non-Claude backends are inconclusive, the overall verdict fails open to the in-session Claude verdict.

Does a disagreement between backends block the audit?▼

No. A disagreement_flag of true is surfaced as residual risk and advisory in the audit report but never hard-blocks on its own. Only a required backend FAIL produces overall_verdict fail, and advisory backends can never flip the overall verdict to fail.