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-architectnpx skills add TheArcForge/Hades --skill unity-architectgit 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.00042 | $0.04833 |
| Opus 5 | $0.00021 | $0.02416 |
| Sonnet 5 | $0.00008 | $0.00967 |
| Haiku 4.5 | $0.00004 | $0.00483 |
Grade A, and why
unity-architect 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 — 590 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Architect
Top-level routing skill for Unity architecture decisions. Provides decision frameworks for component strategy, scene structure, data modeling, prefab architecture, and performance — then routes to specialized sub-skills for deeper implementation guidance.
When to Apply
Activate when the conversation involves:
- Designing a new system or feature from scratch ("how should I structure X?")
- Evaluating trade-offs between architectural approaches
- Scoping a feature before implementation starts
- Asking whether to use MonoBehaviour vs ScriptableObject vs ECS
- Asking how to organize scenes, prefabs, or data
- Performance planning before any profiling has been done
- Cross-cutting concerns: networking, persistence, or testability
Do NOT activate for narrow implementation questions about a specific existing system — those go directly to the relevant sub-skill.
Project Context Check
Before making recommendations:
- Check existing patterns in the graph (always use Hades tools first, not grep/find):
- Call
get_project_summary()to understand project scale, render pipeline, assembly count, asset coverage, and asset volumes — a 200-prefab project warrants different advice than a 20-prefab one - Call
search_by_name("<keyword>", kind="Class")to filter by declaration kind —search_by_namehas no path-prefix or exact-match option anymore; usegraph_query(namePattern: "<keyword>", pathPrefix: "Assets/Scripts")to scope a search to one directory - Call
find_references_to("<script_path>")to discover all dependents — returns both asset references (prefabs, scenes) and C# code references (fields, parameters, inheritance, constructors) - Call
graph_query(edgeKind: "references", edgeTargetNamePattern: "Pool", edgeTargetKind: "Class")or withedgeTargetNamePattern: "Factory"to discover whether spawn infrastructure already exists - Call
graph_query(edgeKind: "references", edgeTargetNamePattern: "GameEvent", edgeTargetKind: "Class")or withedgeTargetNamePattern: "EventChannel"to detect event architecture - Call
trace_dependencies("<CentralSystem>")on any system the new feature depends on to surface tight coupling early
- Call
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 · 590 lines · 42 tokens per session scan A c8f29fcf27d0
unity-architect is a skill published in the GitHub repository TheArcForge/Hades (27 stars, last pushed 6d ago), licensed MIT. It adds 42 tokens to every session and 4,833 once invoked, about $0.0002 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.