moai-ref-cross-model-audit

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

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-ref-cross-model-audit-seung-zedd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-ref-cross-model-audit
Source: https://github.com/Seung-zedd/secure-file-upload/tree/main/.claude/skills/moai-ref-cross-model-audit
Command: npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-ref-cross-model-audit-seung-zedd

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 result into the audit report without corrupting the independence of each backend's opinion. ## Core Features & Use Cases - Single tool surface: Documents the mcp__moai__audit_multi MCP tool, its input parameters (claude_verdict, target, focus, gates, session_id), and its ConvergenceResult output shape including per-backend verdicts, overall verdict, disagreement flag, and residual risk note. - Independence enforcement: Explains the load-bearing rule that secondary backends receive only the target and focus area, never Claude's full analysis, so codex and GLM remain uncorrelated super-reviews. - Convergence policy: Defines the 4-case table mapping required and advisory gate outcomes to overall pass/fail, plus fail-open behavior when optional backends are missing or erroring. - Use Case: An auditor agent reviewing uncommitted changes in a project configured with audit_model: multi loads this Skill, calls audit_multi with its synthesized Claude verdict, and reports a conservative FAIL naming the failing required backend when the models disagree. ## Quick Start Run a multi-model audit of the uncommitted changes by calling the audit_multi tool with my Claude verdict and fold the convergence result into the audit report.

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 object, a target such as uncommittedChanges, and an optional focus area. The tool fans the review out to the codex and GLM backends in parallel and returns a ConvergenceResult with per-backend verdicts and an overall verdict.

When should auditors use cross-model convergence instead of a single backend?▼

Use convergence only when the project's audit_model setting is multi. Single-backend paths (claude, codex, or glm alone) do not load this Skill because no second opinion is needed and the audit_multi tool is the multi-model entry point only.

Why can't I pass Claude's full analysis to the codex and GLM backends?▼

Passing Claude's reasoning would collapse the secondary backends into a re-sample of Claude's opinion, destroying their value as uncorrelated super-reviews. The convergence engine structurally enforces this by sending only the target and focus area to secondary backends.

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

The missing backend returns an inconclusive verdict 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 models block the audit?▼

No. A disagreement_flag of true is surfaced as residual risk and advisory in the audit report, never as a hard block on its own. Only a required-gate FAIL produces a blocking overall_verdict of fail; advisory backend failures are reported but not enforced.