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/team-uinpx skills add frabcd/codex-ai-game-studio --skill team-uigit 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/team-ui)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/team-ui"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/team-ui.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.1 | $0.00057 | $0.02760 |
| Opus 5 | $0.00028 | $0.01380 |
| Sonnet 5 | $0.00011 | $0.00552 |
| Haiku 4.5 | $0.00006 | $0.00276 |
Grade A, and why
team-ui 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 2d 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
88% identical to team-ui — 59 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 — 190 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.
When this skill is invoked, orchestrate the UI team through a structured pipeline.
Decision Points: At each phase transition, use the available user-input mechanism to present
the user with the subagent's proposals as selectable options. Write the agent's
full analysis in conversation, then capture the decision with concise labels.
The user must approve before moving to the next phase.
Phase 0: Resolve Review Mode
- If
--review [mode]was passed as an argument, use that mode. - Else read
production/review-mode.txt— use whatever is written there. - Else default to
lean.
Modes:
full— spawn all director and lead gates as describedlean— skip director gates unless they are PHASE-GATE type (CD-PHASE-GATE, TD-PHASE-GATE, PR-PHASE-GATE, AD-PHASE-GATE)solo— skip all director gate spawning entirely; run the skill without any agent gates
Store the resolved mode for use in all subsequent phases.
Director gate skip rule: Before spawning creative-director, art-director, or any other Tier 1/2 director for review (outside of PHASE-GATE triggers), apply the resolved mode: skip if solo mode; skip if lean mode and this is not a PHASE-GATE.
Team Composition
- ux-designer — User flows, wireframes, accessibility, input handling
- ui-programmer — UI framework, screens, widgets, data binding, implementation
- art-director — Visual style, layout polish, consistency with art bible
- engine UI specialist — Validates UI implementation patterns against engine-specific best practices (read from
.ai-game-studio/project.jsonEngine Specialists → UI Specialist) - accessibility-specialist — Audits accessibility compliance at Phase 4
Templates used by this pipeline:
ux-spec.md— Standard screen/flow UX specificationhud-design.md— HUD-specific UX specificationinteraction-pattern-library.md— Reusable interaction patternsaccessibility-requirements.md— Committed accessibility tier and requirements
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.
- 2d ago First seen · 190 lines · 57 tokens per session scan A e3f13bb9032a
team-ui is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed 5d ago), licensed MIT. It adds 57 tokens to every session and 2,760 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to team-ui, differing in 59 lines, and is treated as a copy.
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.
unity-ui-art-and-motion-production
Use when new or revised Unity UI visuals, icons, panels, 9-slice sprites, component states, HUD or menu layouts, popup motion, screen transitions, or flattened UI screenshot decomposition must be produced through Figma and integrated into uGUI, NGUI, or UI Toolkit; not for UI debugging, localization-only work…