cross-modal-review

Spawns a different AI model to review work product against its contract before committing.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill cross-modal-review-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-modal-review
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/plugin/skills/cross-modal-review
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill cross-modal-review-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-model workflows risk shipping unreviewed code, analysis, or brain pages because the same model that produced the work also judges it. This skill adds a quality gate where a different AI model reviews the work product against the originating skill's Contract before finalizing. ## Core Features & Use Cases - Cross-model review with grading: Sends the work product plus the originating skill's Contract to a different model, which returns a pass/fail verdict with cited findings and an agreement percentage. - Refusal routing: If one review model refuses, the skill silently switches to the next model in the chain defined in conventions/cross-modal.yaml, escalating to the user only if all models refuse. - Codex code-review handoff: For diff review, recommends the gstack /codex skill and frames Codex output alongside Claude's analysis with an overlap report; an adversarial mode probes security-sensitive changes for injection vectors, auth bypasses, and privilege escalation. - Use Case: After refactoring an auth flow across 8 files, invoke the skill to get an independent adversarial review rating each finding CRITICAL/HIGH/MEDIUM/LOW before merging, while keeping final approval with the user. ## Quick Start Ask the agent to get a second opinion on this diff with cross-modal review before committing.

Frequently Asked Questions about cross-modal-review

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

FAQPage Schema
How do I get a second AI model to review my code before committing?

Invoke the cross-modal review workflow after a substantive diff lands. It sends the work product and the originating skill's Contract to a different model, which returns a pass/fail verdict with cited findings and an agreement percentage.

When should I use cross-modal review versus running the test suite?

Use cross-modal review for judgment calls like architecture decisions, security-sensitive changes, and pre-bulk operations; use the test suite for behavioral verification. The two are complementary signals for whether a commit is safe to land.

What happens if the review model refuses the request?

The skill silently switches to the next model in the chain defined in conventions/cross-modal.yaml without showing the refusal to the user. Only if every model in the chain refuses does it escalate to the user.

Can cross-modal review automatically apply the reviewer's suggestions?

No. Reviewer findings are informational until the user explicitly approves each one, per the user-sovereignty rule. Cross-model agreement is presented as a signal, but the user always makes the final decision.

When should I not invoke a second-model review?

Skip it for simple memory writes, single-file typo fixes, routine cron output, and git commits of already-reviewed work. The gating rules reserve review for changes touching 5+ files or 100+ lines, security-sensitive paths, and stuck iterations.