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/uniclaude/prefab-workflownpx skills add TheArcForge/UniClaude --skill prefab-workflowgit clone --depth 1 https://github.com/TheArcForge/UniClaudeWhat 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.00035 | $0.00754 |
| Opus 5 | $0.00017 | $0.00377 |
| Sonnet 5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
prefab-workflow 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prefab Workflow with MCP Tools
Efficient tool sequences for prefab operations.
GOAL: Create a Prefab from Scene Objects
Approach:
- Build the object in the scene first (easier to iterate).
- Once satisfied, save as prefab asset.
- The scene instance becomes a prefab instance automatically.
Tool sequence:
- Build in scene using scene_create_gameobject, component_add, etc.
prefab_create— save scene object as prefab at target path.
Common mistakes:
- Creating parent directories manually — prefab_create handles this.
- Forgetting to save the scene after creating the prefab (scene now has a prefab instance).
GOAL: Edit a Prefab's Properties
Two approaches depending on scope:
Single property change (atomic):
prefab_edit_property— load, edit one property, save. One tool call.
Multi-step changes (session):
prefab_open_editing— opens prefab for editing, returns root path.- Use component_add, component_set_property, reference_set, etc. on the opened prefab's hierarchy.
prefab_save_editing— save and close.
Common mistakes:
- Using prefab_edit_property for many changes (inefficient — opens/saves per call).
- Forgetting prefab_save_editing (changes are lost).
- Trying to use scene tools on a prefab without opening it for editing first.
GOAL: Create a Prefab Variant
Approach:
- Create variant from base prefab.
- Edit the variant's overriding properties.
Tool sequence:
prefab_create_variant— specify base prefab path and new variant path.prefab_edit_property— override specific values on the variant.
Common mistakes:
- Trying to remove components from a variant (not supported — can only add or override).
- Creating deeply nested variants (Base → Variant → Variant) — fragile, avoid.
GOAL: Instantiate Prefabs into the Scene
Approach:
- Instantiate with optional parent.
- Position/configure the instance.
Tool sequence:
prefab_instantiate— create instance in scene, optionally parent it.component_set_propertyon Transform — set position, rotation, scale.reference_set— wire up any scene-specific references.
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.
- 3d ago First seen · 93 lines · 35 tokens per session scan A 34b7030af041
prefab-workflow is a skill published in the GitHub repository TheArcForge/UniClaude (51 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 754 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-ai-behavior
Use when implementing AI and NPC behavior — state machines, behavior trees, GOAP, NavMesh navigation, decision-making patterns, and when to use each approach.
unity-addressables
Use when managing asset loading — Addressables vs Resources vs direct references, async loading patterns, memory management, group strategies, and content update workflows.
unity-audio
Use when implementing audio systems — audio manager architecture, AudioMixer setup, spatial audio, event-driven audio, music systems, and sound effect management patterns.
unity-ecs
Use when considering ECS/DOTS architecture — when to use ECS vs MonoBehaviour, Burst compiler, Job System, hybrid approaches, and migration strategies from MonoBehaviour to ECS.
unity-input
Use when implementing input handling — new Input System setup, action maps, multi-device support, input rebinding, local multiplayer input, and input abstraction patterns.