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 agentmods add skills/frabcd/codex-ai-game-studio/code-reviewnpx skills add frabcd/codex-ai-game-studio --skill code-reviewgit clone --depth 1 https://github.com/frabcd/codex-ai-game-studioWrote 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/frabcd/codex-ai-game-studio/code-review)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/code-review"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/code-review.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.01863 |
| Opus 5 | $0.00020 | $0.00932 |
| Sonnet 5 | $0.00008 | $0.00373 |
| Haiku 4.5 | $0.00004 | $0.00186 |
Grade A, and why
code-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Port provenance: adapted from the pinned upstream source at
984023ddac0d5e27624f2baacde6105e45de375funder MIT; see the repository parity ledger for the exact path and blob.
Phase 1: Load Target Files
Read the target file(s) in full. Read AGENTS.md for project coding standards.
Phase 2: Identify Engine Specialists
Read .ai-game-studio/project.json, section ## Engine Specialists. Note:
- The Primary specialist (used for architecture and broad engine concerns)
- The Language/Code Specialist (used when reviewing the project's primary language files)
- The Shader Specialist (used when reviewing shader files)
- The UI Specialist (used when reviewing UI code)
If the section reads [TO BE CONFIGURED], no engine is pinned — skip engine specialist steps.
Phase 3: ADR Compliance Check
Argument: $ai-game-studio:code-review [file(s)] may optionally include a story file path as the last argument (e.g., $ai-game-studio:code-review src/combat/attack.gd production/epics/combat/story-001.md). If a story path is provided, read it to extract the governing ADR reference.
Search for ADR references in, in priority order:
- The story file (if provided as argument)
- Header comments at the top of the implementation files
- Commit messages referencing these files (
git log --oneline -- [file])
Look for patterns like ADR-NNN or docs/architecture/ADR-.
If no ADR references found, note: "No ADR references found — ADR compliance check skipped. For full ADR compliance review, provide the story path: $ai-game-studio:code-review [files] [story-path]."
For each referenced ADR: read the file, extract the Decision and Consequences sections, then classify any deviation:
- ARCHITECTURAL VIOLATION (BLOCKING): Uses a pattern explicitly rejected in the ADR
- ADR DRIFT (WARNING): Meaningfully diverges from the chosen approach without using a forbidden pattern
- MINOR DEVIATION (INFO): Small difference from ADR guidance that doesn't affect overall architecture
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 187 lines · 41 tokens per session scan A d8c4ae4878c4
code-review is a skill published in the GitHub repository frabcd/codex-ai-game-studio (8 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 1,863 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
iso-24495-2
Sector-specific Plain Language standard for legal communication (ISO 24495-2:2025). Applied during contract drafting, license review, and legal/compliance writing.
compensation-calculator
Calculate worker-side monetary claim ranges for China labor disputes, including N, N+1, 2N, unpaid wages, unsigned-contract double wage, and unused annual leave estimates. Use when case facts include employment dates, wage, termination path, or the user asks how much compensation to request.
usd-tools
Infrastructure skill — low-level OpenUSD scene inspection and validation: read layer stacks, traverse prims, validate USD schemas. Use when working directly with raw USD files (usda, usdc, usdz) or verifying USD compliance. Not for Maya-specific USD export — use maya-pipelineexportusd for that. Not for full DCC…
local-rules-adapter
Route China worker-rights cases through city-specific labor-rule checks, local wage-cap verification, social-insurance or housing-fund source lookup, arbitration venue/form checks, and source-card status labels. Use when a case involves Beijing, Shanghai, Shenzhen, Guangzhou, Hangzhou, a local average-wage cap, local…
agreement-review
Use when a China-mainland worker needs help before or after signing, countersigning, negotiating, or relying on a separation, resignation, termination, non-compete, confidentiality, service-period, waiver, liquidated-damages, handover, or settlement-payment document.
arbitration-drafter
Draft worker-side China labor arbitration application materials from structured facts, claims, compensation calculations, evidence, agreement risks, and source-card anchors. Use when a worker is preparing to file labor arbitration for dismissal, layoff, forced resignation, unpaid wages, unsigned contract double wage…