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 commands/xeldaralz/everything-claude-unity/unity-uigit clone --depth 1 https://github.com/XeldarAlz/everything-claude-unityWrote 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/commands/xeldaralz/everything-claude-unity/unity-ui)<a href="https://agentmods.dev/commands/xeldaralz/everything-claude-unity/unity-ui"><img src="https://agentmods.dev/badge/commands/xeldaralz/everything-claude-unity/unity-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 | $0.00025 | $0.00284 |
| Opus 5 | $0.00013 | $0.00142 |
| Sonnet 5 | $0.00005 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
unity-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 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.
What it actually says
/unity-ui — Build a UI Screen
Build a UI screen based on: $ARGUMENTS
Workflow
Use the unity-ui-builder agent to:
- Choose UI system — UGUI (Canvas) or UI Toolkit based on project context
- Plan the layout — identify elements, hierarchy, interaction, styling
- Write scripts:
- UGUI: MonoBehaviour with
[SerializeField]Button/Text/Image references - UI Toolkit: UXML document + USS stylesheet + controller script
- UGUI: MonoBehaviour with
- Build visual hierarchy via MCP:
- UGUI: Canvas, panels, buttons, text via
manage_ui+manage_gameobject - UI Toolkit: write UXML/USS files, attach UIDocument component
- UGUI: Canvas, panels, buttons, text via
- Wire interactions — button clicks, input fields, toggles
- Verify via
read_console
UGUI Performance Rules
- Disable Raycast Target on non-interactive elements
- Split static/dynamic content into separate Canvases
- Avoid Layout Groups in scroll views
Report the screen structure, scripts created, and how to test.
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 · 33 lines · 25 tokens per session scan A c489321ee43a
unity-ui is a command published in the GitHub repository XeldarAlz/everything-claude-unity (21 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 284 once invoked, about $0.0001 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 commands, from other repositories
sim
Run the EmbodiedGen simulation rendering workflow with sim-cli.
speckit.taskstoissues
Command "speckit.taskstoissues" from akiojin/unity-mcp-server, covering ユーザー入力 and 実行手順.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
tech-debt
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.