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/valkor-ai/loom/animationnpx skills add valkor-ai/loom --skill animationgit clone --depth 1 https://github.com/valkor-ai/loomWrote 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/valkor-ai/loom/animation)<a href="https://agentmods.dev/skills/valkor-ai/loom/animation"><img src="https://agentmods.dev/badge/skills/valkor-ai/loom/animation.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.00075 | $0.00343 |
| Opus 5 | $0.00037 | $0.00171 |
| Sonnet 5 | $0.00015 | $0.00069 |
| Haiku 4.5 | $0.00007 | $0.00034 |
Grade A, and why
animation-review 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 5d 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
Animation Review
Post-implementation reviewer for Godot animation code. Checks against known gotchas that LLMs consistently get wrong.
When to trigger
After animation-related code is written or modified. Look for:
- Animation nodes (AnimationPlayer, AnimationTree, AnimatedSprite2D)
- AnimationTree state machine control (
travel(),start(),active) - SpriteFrames or Animation resource manipulation at runtime
callback_mode_processsettings- Pool/spawn lifecycle involving animated entities
- Briefs or asset snapshots that require multi-frame
grid_sheetruntime assets, dynamic-mode evidence, frame sequences, animated actors, or animated FX. Trigger even if the implementation contains no animation API; omitted expected animation is a finding.
Review process
- Read
gotchas.md - Scan the implemented code against each gotcha
- For each hit:
- Cite the gotcha ID (e.g. G1)
- Show the offending code
- Provide the fix
- If no hits, report clean
- Optionally run
checklist.mdstatic checks for automated verification
When you need specific API details, delegate to the godot-api skill.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 40 lines · 75 tokens per session scan A c1a9f16ec8bc
animation-review is a skill published in the GitHub repository valkor-ai/loom (960 stars, last pushed 19d ago), licensed Apache-2.0. It adds 75 tokens to every session and 343 once invoked, about $0.0004 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
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…