cross-modal-review

Spawn secondary AI models to review work against contractual requirements.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/starlink-awaken/omostation-gbrain --skill cross-modal-review-starlink-awaken
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-modal-review
Source: https://github.com/starlink-awaken/omostation-gbrain/tree/main/skills/cross-modal-review
Command: npx skills add https://github.com/starlink-awaken/omostation-gbrain --skill cross-modal-review-starlink-awaken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of AI hallucination and oversight by implementing a mandatory second-opinion quality gate before finalizing critical work.

Core Features & Use Cases

  • Refusal Routing: Automatically switches to a secondary model if the primary reviewer refuses a request, ensuring continuous validation.
  • Contract-Based Grading: Evaluates work against the originating skill's specific promises rather than subjective quality.
  • Adversarial Challenge: Performs security-focused reviews to identify potential injection vectors, race conditions, and data leaks.

Quick Start

Invoke the cross-modal-review skill to perform an adversarial check on the current code diff before committing your changes.

Frequently Asked Questions about cross-modal-review

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

FAQPage Schema
How do I perform a multi-model code review to catch AI hallucinations?

Multi-model code review catches AI hallucinations by spawning secondary AI models to perform independent reviews against defined contractual requirements. This mandatory second-opinion quality gate verifies work products objectively before finalizing critical work.

What is adversarial security testing for code diffs and when do I need it?

Adversarial security testing for code diffs identifies potential injection vectors, race conditions, and data leaks before committing changes. You need this security-focused review to ensure high-integrity output and prevent vulnerabilities when finalizing critical work.

How do I validate code against specific contract requirements instead of subjective quality?

Contract-based grading validates code by evaluating work against the originating skill's specific promises rather than subjective quality metrics. This approach ensures the output meets defined contractual requirements through an objective, multi-model consensus verification process.

Can I use model routing to bypass AI refusals during automated code reviews?

Model routing bypasses AI refusals during automated code reviews by automatically switching to a secondary model if the primary reviewer refuses a request. This refusal-aware routing ensures continuous validation without manual intervention or workflow disruption.

Do I need git-diff context to run an independent multi-model security check?

You need git-diff context to run an independent multi-model security check because it provides the necessary code changes for objective review. The validation process requires this integration with model-routing conventions to ensure high-integrity output and accurate adversarial testing.