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 frabcd/codex-ai-game-studio --skill ux-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/ux-review)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/ux-review"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/ux-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/frabcd/codex-ai-game-studio/ux-review"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/ux-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.02560 |
| Opus 5 | $0.00026 | $0.01280 |
| Sonnet 5 | $0.00010 | $0.00512 |
| Haiku 4.5 | $0.00005 | $0.00256 |
Grade A, and why
ux-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 5d 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 — 265 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.
Overview
Validates UX design documents before they enter the implementation pipeline.
Acts as the quality gate between UX Design and Visual Design/Implementation in
the $ai-game-studio:team-ui pipeline.
Run this skill:
- After completing a UX spec with
$ai-game-studio:ux-design - Before handing off to
ui-programmerorart-director - Before the Pre-Production to Production gate check (which requires key screens to have reviewed UX specs)
- After major revisions to a UX spec
Verdict levels:
- APPROVED — spec is complete, consistent, and implementation-ready
- NEEDS REVISION — specific gaps found; fix before handoff but not a full redesign
- MAJOR REVISION NEEDED — fundamental issues with scope, player need, or completeness; needs significant rework
Phase 1: Parse Arguments
- Specific file path (e.g.,
$ai-game-studio:ux-review design/ux/inventory.md): validate that one document all: find all files indesign/ux/and validate eachhud: validatedesign/ux/hud.mdspecificallypatterns: validatedesign/ux/interaction-patterns.mdspecifically- No argument: ask the user which spec to validate
For all, output a summary table first (file | verdict | primary issue) then
full detail for each.
Phase 2: Load Cross-Reference Context
Before validating any spec, load:
- Input & Platform config: Read
.ai-game-studio/project.jsonand extract## Input & Platform. This is the authoritative source for which input methods the game supports — use it to drive the Input Method Coverage checks in Phase 3A, not the spec's own header. If unconfigured, fall back to the spec header. - The accessibility tier committed to in
design/accessibility-requirements.md(if it exists) - The interaction pattern library at
design/ux/interaction-patterns.md(if it exists) - The GDDs referenced in the spec's header (read their UI Requirements sections)
- The player journey map at
design/player-journey.md(if it exists) for context-arrival validation
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.
- 5d ago First seen · 265 lines · 51 tokens per session scan A f1b1d998d7e2
ux-review is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 2,560 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
use-widget-asset
Use when consuming a widget slice (panel, button, slider, progress bar, or toggle pair) from a create-asset-sheet pack in a Summer Engine scene. The pack's metadata.sliceMeta carries 9-slice margins, fill rects, and on/off pair links per slice. This skill explains how to wire those into NinePatchRect…
ui-basics
Use when building Summer Engine UI: HUDs, main menus, pause menus, health bars, progress bars, dialogue boxes, or any Control-node tree. Covers anchors, containers (VBox/HBox/Margin), responsive layout, and theme versus inline styling. Trigger on "UI", "HUD", "menu", "health bar", "Control", "anchors"…
genre-card-party-idle
Art direction for card games, deck builders, party games, idle/incremental, educational, and rhythm game presentational spaces in Blender.
genre-narrative-vn
Art direction for visual novel, interactive movie, walking simulator, and story-driven presentation spaces in Blender.
genre-survival
Art direction for survival and survival-horror gameplay spaces in Blender emphasizing resource props, crafting readability, and tension routes.
game-ui
Design HUDs, menus and diegetic interfaces with controller navigation and readability at TV distance. Use when designing HUDs, inventory menus, or controller-first interfaces.