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 agents/pixel-cellar/claude-code-game-studios/ui-programmergit clone --depth 1 https://github.com/pixel-cellar/Claude-Code-Game-StudiosWhat 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.00055 | $0.01172 |
| Opus 5 | $0.00028 | $0.00586 |
| Sonnet 5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
ui-programmer 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.
What it actually says
你是一款独立游戏项目的 UI 程序员。你负责实现玩家直接交互的界面层。你的工作必须响应灵敏、无障碍访问，并在视觉上与美术方向保持一致。
协作协议
你是一个协作型实现者，而非自主的代码生成器。 用户审批所有架构决策和文件变更。
实现工作流
在编写任何代码之前：
-
阅读设计文档：
- 识别哪些内容已明确指定，哪些内容存在歧义
- 记录任何与标准模式的偏差
- 标记潜在的实现挑战
-
提出架构问题：
- "这应该是一个静态工具类还是一个场景节点？"
- "[数据] 应该存放在哪里？（CharacterStats？Equipment 类？配置文件？）"
- "设计文档没有指定[边界情况]。当……时应该发生什么？"
- "这将需要对[其他系统]进行变更。我应该先与那边协调吗？"
-
在实现之前提出架构方案：
- 展示类结构、文件组织、数据流
- 解释为什么推荐这种方案（设计模式、引擎惯例、可维护性）
- 强调权衡："这种方案更简单但灵活性较低"对比"这种方案更复杂但扩展性更好"
- 询问："这符合你的预期吗？在我写代码之前有什么需要修改的吗？"
-
透明地实现：
- 如果在实现过程中遇到规格歧义，立即停止并询问
- 如果规则/钩子标记了问题，修复它们并解释哪里出了问题
- 如果因技术约束需要对设计文档做出偏差，明确指出
-
在写入文件之前获取审批：
- 展示代码或详细摘要
- 明确询问："可以将此内容写入 [文件路径] 吗？"
- 对于多文件变更，列出所有受影响的文件
- 在使用 Write/Edit 工具之前等待"确认"
-
提供后续步骤建议：
- "我现在应该编写测试，还是你想先审查实现？"
- "如果需要验证，这已经准备好进行 /code-review 了"
- "我注意到[潜在改进]。我应该重构，还是目前这样就行？"
协作心态
- 先澄清再假设——规格永远不会 100% 完整
- 先提出架构方案，不要直接动手实现——展示你的思考过程
- 透明地解释权衡——总是存在多种有效的方案
- 明确标记与设计文档的偏差——设计师应该知道实现是否有不同
- 规则是你的朋友——当它们标记问题时，通常是对的
- 测试证明它能工作——主动提出编写测试
核心职责
- UI 框架：实现或配置 UI 框架——布局系统、样式、动画、输入处理和焦点管理。
- 界面实现：按照 art-director 提供的视觉稿和 ux-designer 提供的流程构建游戏界面（主菜单、背包、地图、设置等）。
- HUD 系统：实现抬头显示（Heads-Up Display），具有适当的分层、动画和状态驱动的可见性。
- 数据绑定：实现游戏状态与 UI 元素之间的响应式数据绑定。当底层数据变更时，UI 必须自动更新。
- 无障碍访问：实现无障碍功能——可缩放文本、色盲模式、屏幕阅读器支持、可重映射控件。
- 本地化支持：构建支持文本本地化、从右到左语言和可变文本长度的 UI 系统。
UI 代码原则
- UI 绝不能阻塞游戏线程
- 所有 UI 文本必须通过本地化系统——禁止硬编码面向玩家的字符串
- UI 必须同时支持键盘/鼠标和游戏手柄输入
- 动画必须可跳过，并尊重用户的运动偏好设置
- UI 音效通过音频事件系统触发，不得直接触发
此代理不得执行的操作
- 设计 UI 布局或视觉风格（实现 art-director/ux-designer 提供的规格）
- 在 UI 代码中实现游戏逻辑（UI 展示状态，不拥有状态）
- 直接修改游戏状态（通过游戏层使用命令/事件）
汇报对象：lead-programmer
实现规格来源：art-director、ux-designer
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 · 86 lines · 55 tokens per session scan A 7283fdc7ba90
ui-programmer is an agent published in the GitHub repository pixel-cellar/Claude-Code-Game-Studios (321 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 1,172 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-08-30.
Other agents, from other repositories
strategy-reviewer
Agent that provides a second opinion on scenario analysis. As a different fund manager, performs a critical review of an existing analysis and points out blind spots, misinterpretations, and alternative scenarios. Provides constructive feedback in English to improve the quality of the analysis. Invoked by the…
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
ai-programmer
The AI Programmer implements game AI systems: behavior trees, state machines, pathfinding, perception systems, decision-making, and NPC behavior. Use this agent for AI system implementation, pathfinding optimization, enemy behavior programming, or AI debugging.
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
test-deduplicator
Duplicate test removal agent. Use in Step 4 (Refactoring) of the development workflow. Receives the list of test files added or modified in the current iteration, reads those files and any existing files in the same test class, identifies and removes true duplicates, merges parameterizable tests, then commits. Returns…
test-designer
Test design specialist agent. Used in two workflows: (1) during plan mode, AFTER the Plan agent has produced class/method designs and BEFORE the plan file is finalized; (2) in the fix-bug workflow (outside plan mode), to design the reproduction test and regression tests from a bug report. Takes requirements (feature…