Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/cynthiajones34/GBrainnpx agentmods add skills/cynthiajones34/gbrain/cross-modal-reviewWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cynthiajones34/gbrain/cross-modal-review)<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/cross-modal-review"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/cross-modal-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/cross-modal-review"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/cross-modal-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00076 | $0.01547 |
| Opus 5 | $0.00038 | $0.00773 |
| Sonnet 5 | $0.00015 | $0.00309 |
| Haiku 4.5 | $0.00008 | $0.00155 |
Grade A, and why
cross-modal-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to cross-modal-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Modal Review
Convention: see conventions/cross-modal.yaml for the review pairs and refusal routing chain.
Relationship to
gbrain eval cross-modal: This skill is the manual mid-flow gate (one model reviews work product before commit, with refusal routing). Thegbrain eval cross-modalcommand (v0.27.x) is a sibling surface: 3 different-provider frontier models score-and-iterate on a documented dimension list before tests cement behavior. Use this skill for ad-hoc second opinions; usegbrain eval cross-modalfor the skillify Phase 3 quality gate. The two are complementary, not redundant.
Contract
This skill guarantees:
- Work product is reviewed by a different model before finalizing.
- The review is graded against the originating skill's Contract section (what was promised), not vibes.
- Agreement and disagreement are reported transparently.
- Refusal from one model triggers a silent switch to the next in chain.
- The user always makes the final decision (user sovereignty).
When to invoke (v0.25.1 gating)
Invoke this skill when:
- Significant code changes — any commit touching 5+ files or 100+ lines. Architecture decisions, refactors, API changes.
- Security-sensitive changes — auth flows, brain-write trust boundaries, webhook transforms, cross-skill data passing.
- Stuck or churning — 2+ iterations on the same problem without progress.
- Pre-bulk-operation — before running batch enrichment, migrations, or bulk writes (see conventions/test-before-bulk.md).
- Skill creation / modification — new or rewritten skills that affect operational behavior.
- Brain-page quality concerns — when brain writes need validation against the originating skill's Contract.
Do NOT invoke for:
- Simple memory writes or brain-page updates
- Single-file typo fixes
- Routine cron output or heartbeat operations
- Git commit / push of already-reviewed work
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 198 lines · 76 tokens per session scan A 685233b1afd4
cross-modal-review is a skill published in the GitHub repository cynthiajones34/GBrain (0 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,547 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cross-modal-review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
dx-roaster
Brutally honest developer-experience audit for a GitHub repo. Scores 10 DX dimensions (time-to-first-success, README clarity, visual proof, install, quick-start, docs, examples, community, trust, marketing), writes a shareable roast in the requested tone (brutal/honest/kind), produces a prioritized action plan ranked…
code-knowledge-graph
Codebase'i knowledge graph olarak analiz et. Dependency, call graph, hotspot analizi.
cortex-memory
Persistent cognitive memory for AI agents — query, record, review, and consolidate knowledge across sessions with spreading activation, FSRS scheduling, and NLI contradiction detection.
hermes-change-review
Use when a branch, pull request, Kanban task, or implementation must be reviewed separately for intent fidelity, repository quality, and verification evidence before completion or merge is accepted.
stage-refactor-checklist
Comprehensive checklist for refactoring a schemacompiler stage folder. Use EVERY TIME you refactor a compiler stage (resolve, unify, codegen, etc.). Read this before writing any code.