Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add babyworm/rtl-agent-team --skill codex-cross-reviewgit clone --depth 1 https://github.com/babyworm/rtl-agent-teamWrote 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/babyworm/rtl-agent-team/codex-cross-review)<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/codex-cross-review"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/codex-cross-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/babyworm/rtl-agent-team/codex-cross-review"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/codex-cross-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.00035 | $0.01145 |
| Opus 5 | $0.00017 | $0.00573 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade B, and why
codex-cross-review scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
The skill reads `~/.codex/config.toml` for model and effort settings. How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- Phase boundary: before declaring any phase (1-6) complete
- Manual invocation: user wants independent cross-review of current work
- Quality gate: need a second opinion from a different model family </Use_When>
<Do_Not_Use_When>
- Codex CLI is not installed (check with
codex --version) - Work is still in progress (cross-review should happen on completed deliverables)
- Phase 7 exploration (exempt from pipeline gates) </Do_Not_Use_When>
Prerequisites
- Codex CLI installed:
codex --versionmust succeed - OpenAI API key configured: Codex must be authenticated
- Phase artifacts exist: the phase being reviewed must have produced deliverables
Configuration
The skill reads ~/.codex/config.toml for model and effort settings.
Users configure their preferred model and reasoning effort there — the skill never overrides these.
Display the current config to the user at the start of every invocation:
Codex Config: model={model}, reasoning_effort={effort}
Execution
Phase Auto-Detection
If no phase number is provided, detect the current phase from:
- Most recently modified
docs/phase-N-*/directory - Ask user if ambiguous
Spawn Cross-Reviewer Agent
Task(subagent_type="rtl-agent-team:codex-cross-reviewer",
prompt="Run cross-review for Phase {N}.
Phase intent: {brief description from phase docs}.
Target artifacts: {list of docs/code paths}.
Changed files: {from git diff}.")
Integration Protocol (for Phase Orchestrators)
Phase orchestrators (P1-P6) should invoke cross-review as their penultimate step (before declaring phase complete):
# In orchestrator agent prompt, before final step:
Step N-1: Cross-Review Gate
Task(subagent_type="rtl-agent-team:codex-cross-reviewer",
prompt="Cross-review Phase {N}. Artifacts: {paths}.")
# MANDATORY explicit verdict check:
Read(".rat/cross-review/phase-{N}/cross-review-report.md")
# Parse verdict field — must be CONSENSUS or USER_DECIDED
# If verdict != CONSENSUS and user did not approve → do NOT proceed to completion
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.
- 8d ago First seen · 113 lines · 35 tokens per session scan B b4f02cdbf0cf
codex-cross-review is a skill published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 18d ago), licensed MIT. It adds 35 tokens to every session and 1,145 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
qa-review
QA review for code changes — test coverage analysis, edge case identification, test plan generation, regression detection, test health tracking over time.
readable-verilog-generator
Use when creating, writing, reviewing, annotating, repairing, refactoring, or validating readable Verilog RTL, including synthesizable Verilog-2001 .v files, existing-RTL analysis, semantic comment annotation, testbench scaffold planning, ASIC-quality review, local or remote Vivado/xsim validation, evidence-backed…
aster-review-ci
Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers aster review --pr, --json, --stream, --comment, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.
fresh-eyes-loop
A repeatable quality-review process using two independent agents: one reviews and verifies, while the other fixes issues. P0 and P1 mean the highest-severity problem levels.
kicad-pcb-review
Use this skill when reviewing, fixing, validating, or preparing KiCad PCB projects with the kicad MCP server.
rtl-review
Audit RTL code for lint violations, synthesis hazards, coding-style compliance, and readability. Use when the user says "review this Verilog", "check my RTL", "lint this module", "is this code synthesizable", or shares an HDL file and asks for feedback before simulation or tape-in.