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/animation-workflownpx skills add TheArcForge/UniClaude --skill animation-workflowgit clone --depth 1 https://github.com/TheArcForge/UniClaudeWrote 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/skills/thearcforge/uniclaude/animation-workflow)<a href="https://agentmods.dev/skills/thearcforge/uniclaude/animation-workflow"><img src="https://agentmods.dev/badge/skills/thearcforge/uniclaude/animation-workflow.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.00035 | $0.00785 |
| Opus 5 | $0.00017 | $0.00392 |
| Sonnet 5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
animation-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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Animation Workflow with MCP Tools
Efficient tool sequences for animation setup.
GOAL: Create an Animator Controller from Scratch
Approach:
- Create the controller with all parameters, states, and transitions in one call.
- Assign clips to states.
- Assign controller to GameObject.
Tool sequence:
animation_create_controller— single batch call creates the full state machine:- Parameters (bool, float, int, trigger)
- States with motion clip references
- Transitions with conditions
animation_assign_clip— assign AnimationClip assets to states (if not set during creation).animation_assign_controller— apply controller to a GameObject (adds Animator if missing).
Common mistakes:
- Creating empty controller then adding states one by one (inefficient — use the batch call).
- Forgetting to set a default state (first state added is default).
- Not creating parameters before referencing them in transition conditions.
GOAL: Edit an Existing Controller
Approach:
- Inspect current state.
- Batch add/remove operations.
Tool sequence:
animation_get_controller— inspect parameters, states, transitions, layers.animation_edit_controller— batch modify: add/remove parameters, states, transitions.
Common mistakes:
- Removing a state that other transitions reference (leaves dangling transitions).
- Adding duplicate parameter names (will error).
GOAL: Configure Animation Clip Import Settings
When to use: Setting loop behavior, frame ranges on FBX/model animation clips.
Tool sequence:
asset_get_import_settings— read current clip settings on the model.asset_set_clip_import_settings— set loopTime, loopPose, start/end frames per clip.
Common mistakes:
- Setting loop on the wrong clip name (FBX can have multiple clips — check names first).
- Forgetting that import setting changes require reimport (the tool handles this automatically).
GOAL: Set Up a Character with Animations
Full workflow example:
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 · 90 lines · 35 tokens per session scan A 4730cc5def22
animation-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 785 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.