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 skills add PracticalSwan/agent-skills --skill figma-use-motiongit clone --depth 1 https://github.com/PracticalSwan/agent-skillsWrote 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/practicalswan/agent-skills/figma-use-motion)<a href="https://agentmods.dev/skills/practicalswan/agent-skills/figma-use-motion"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/figma-use-motion/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/practicalswan/agent-skills/figma-use-motion"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/figma-use-motion.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00058 | $0.02208 |
| Opus 5 | $0.00029 | $0.01104 |
| Sonnet 5 | $0.00012 | $0.00442 |
| Haiku 4.5 | $0.00006 | $0.00221 |
Grade A, and why
figma-use-motion 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
use_figma — Figma Plugin API Skill for Motion
Motion context for the use_figma MCP tool. figma-use covers the foundational Plugin API rules — load both together.
Always pass skillNames: "figma-use-motion" (comma-separated alongside figma-use) when calling use_figma for motion work. Logging only.
Runtime Gating
Motion APIs are gated behind the metronome user feature flag. When the calling user doesn't have it, every motion property and helper referenced in this skill throws "<name>" is not a supported API.
Bail out fast on that error. Do not retry; tell the user motion isn't enabled for them and stop. Otherwise you'll burn calls and confuse the user with repeated identical failures.
When to use this skill
Load this skill whenever a use_figma task involves:
- Adding, editing, or removing keyframes on a node (
manualKeyframeTracks,applyManualKeyframeTrack,removeManualKeyframeTrack). - Animating fill or stroke colors over time.
- Applying, editing, or removing animation styles (
applyAnimationStyle,removeAnimationStyle,animationStyles). - Reading or writing timeline duration via
node.timelines/node.setTimelineDuration(id, seconds). - Choosing easing for any of the above.
Static design work (creating shapes, components, variables, layout) goes through figma-use alone — this skill is only for the time dimension.
Exposed motion API surface
node.manualKeyframeTracks— read/write manual keyframes (including fill, stroke, and effect tracks).node.applyManualKeyframeTrack(field, track)/node.removeManualKeyframeTrack(field)— add, replace, or remove one manual keyframe track without rewriting the whole object.node.animationStyles— read/write animation-style metadata applied to a node.node.applyAnimationStyle(styleId, presetData?)/node.removeAnimationStyle(id)— apply a discovered style and remove an applied style instance by its returned/read-backid.node.timelines— read-only timeline list for the containing top-level frame, with durations in seconds.node.setTimelineDuration(id, durationSeconds)— write the containing top-level frame timeline duration.node.animations— read-only resolved keyframe data (currently manual tracks only — see motion-patterns.md).figma.motion.figmaAnimationStyles()— read-only list of Figma's first-party animation styles.
What ships with it
3 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.
- 2d ago Changed ab238beb00c0
- 4d ago Changed 6877db698333
- 7d ago First seen · 132 lines · 58 tokens per session scan A afcbc8dec924
figma-use-motion is a skill published in the GitHub repository PracticalSwan/agent-skills (14 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 2,208 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
create-component-md
Generate a canonical JSON contract and a self-contained implementation Markdown specification for a Figma component covering API, structure, color, and screen-reader behavior. Reads a base.json produced by the uSpec Extract plugin, runs four read-only interpretation skills in parallel, reconciles their outputs, and…
create-color
Generate color annotation specifications mapping UI elements to design tokens. Use when the user mentions "color", "color annotation", "color spec", "tokens", "design tokens", or wants to document which color tokens a component uses.
figma-build
Build a Figma design from code or a description — the reverse of figma-codegen. Reuses the connected file's existing design system (components, variables, styles) instead of drawing primitives with hardcoded values. Triggers whenever the user wants something created or updated IN Figma from code or a spec — e.g.…
extract-api
Interpret a component's API (properties, sub-components, configuration examples) from the base.json produced by the uSpec Extract Figma plugin, and write the normalized JSON to disk. Read-only interpretation — no Figma calls except an optional tiny delta script. Use as a sub-skill of create-component-md.
extract-color
Interpret a component's color-token mapping (per-element fills/strokes/effects, axis classification, boolean delta, variable mode detection, strategy plan) from the base.json produced by the uSpec Extract Figma plugin, and write the normalized JSON to disk. Read-only interpretation — no Figma calls except an optional…