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/thearcforge/hades/unity-uinpx skills add TheArcForge/Hades --skill unity-uigit clone --depth 1 https://github.com/TheArcForge/HadesWhat 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.00029 | $0.05395 |
| Opus 5 | $0.00015 | $0.02697 |
| Sonnet 5 | $0.00006 | $0.01079 |
| Haiku 4.5 | $0.00003 | $0.00539 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 674 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity UI
Guidance for building Unity interfaces: choosing between UI Toolkit and uGUI, laying out flexible screens, wiring data to views, managing dialog stacks, and structuring persistent HUDs.
When to Apply
Activate when the conversation involves:
- Deciding whether to use UI Toolkit or uGUI for a new screen or feature
- Laying out panels, lists, or HUD elements that must adapt to different resolutions
- Creating dialog, popup, or modal systems with open/close navigation
- Binding runtime data (health, score, inventory) to visible UI elements
- Structuring a persistent HUD overlay that receives frequent updates
- Reviewing a UI script that has become large or is updating every frame unnecessarily
- Setting up UXML/USS templates or Canvas prefabs for reuse
Do NOT activate for questions purely about animations on UI elements (see hades:animation-workflow), 3D world-space labels attached to game objects, or input handling that only happens to trigger UI (see hades:unity-input).
Project Context Check
Before making recommendations:
-
Detect what UI system is already in use:
- Call
graph_query(edgeKind: "references", edgeTargetNamePattern: "UIDocument", edgeTargetKind: "Class")to see if UI Toolkit documents are present - Call
graph_query(edgeKind: "references", edgeTargetNamePattern: "Canvas", edgeTargetKind: "Class")to see if uGUI canvases exist - Call
search_by_name("*.uxml")to find UXML templates already authored - Call
search_by_name("*.uss")to find USS stylesheets in the project
- Call
-
Check recorded decisions in memory:
- Call
recall_memory("UI architecture toolkit uGUI")to find any documented UI strategy - If a recalled decision shows
warning, surface the conflict to the user before proceeding
- Call
-
Adapt recommendations based on findings:
- If both
UIDocumentandCanvasare present → the project is mixed; establish which system owns which surface before adding more UI - If only
Canvasis found → recommend uGUI unless there is a strong reason to introduce UI Toolkit - If only
UIDocumentis found → stay in UI Toolkit; do not introduce uGUI without a clear reason (e.g., world-space) - After the user agrees on an approach not yet documented, call
propose_memory_updateto record the decision
- If both
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 · 674 lines · 29 tokens per session scan A dc035af2e38d
unity-ui is a skill published in the GitHub repository TheArcForge/Hades (27 stars, last pushed 6d ago), licensed MIT. It adds 29 tokens to every session and 5,395 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 skills, from other repositories
octocode-mannequin
Use when posing, animating, or explaining a 3D human skeleton/manikin: anatomical joints, ROM clamps, walk/run/dance/backflip sequences, Three.js viewer, or agent-driven WebMCP figure control (reach/lookat). Phrases like pose the manikin, skeleton scheme, animate a walk cycle. Not for general 3D scenes…
unity-reviewer
Use after implementation to review code changes for Unity anti-patterns, performance issues, and correctness problems. Also use when superpowers:requesting-code-review is active to provide Unity-specific review criteria.
component-design
Use when you need detailed decision frameworks for MonoBehaviour composition, inter-component communication, single responsibility, and execution order.
data-modeling
Use when you need detailed decision frameworks for ScriptableObject patterns, runtime data management, serialization strategies, and data-driven architecture.
prefab-architecture
Use when you need detailed decision frameworks for prefab vs variant vs ScriptableObject, nested prefab design, override strategies, and prefab editing workflows.
scene-architecture
Use when you need detailed decision frameworks for scene structure, additive loading, scene management, transitions, and persistent managers.