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 taotao135791-bit/gsap-transform --skill motion-studiogit clone --depth 1 https://github.com/taotao135791-bit/gsap-transformWrote 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/taotao135791-bit/gsap-transform/motion-studio)<a href="https://agentmods.dev/skills/taotao135791-bit/gsap-transform/motion-studio"><img src="https://agentmods.dev/badge/skills/taotao135791-bit/gsap-transform/motion-studio/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/taotao135791-bit/gsap-transform/motion-studio"><img src="https://agentmods.dev/badge/skills/taotao135791-bit/gsap-transform/motion-studio.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.00180 | $0.03926 |
| Opus 5.5 | $0.00072 | $0.01570 |
| Sonnet 5.5 | $0.00036 | $0.00785 |
| Haiku 4.5 | $0.00018 | $0.00393 |
Grade A, and why
motion-studio 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 1mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Motion Studio (Video Delivery Shell)
The layer that turns an animated GSAP scene into a video artifact: a self-contained folder the user opens in a browser, scrubs on a timeline, tunes by chat, and renders to a multi-resolution mp4. This is the bridge from "GSAP web animation" to "the user gets an .mp4" — the missing end of the pipeline that /export (motion-craft) only sketched.
It is a delivery shell, not a design skill. Aesthetic direction still comes from motion-design-taste; editable timeline state comes from motion-state and motion-primitives; GSAP API details come from the gsap-* skills. Motion Studio owns only the preview/export mechanics.
When to Use This Skill
Apply when the user wants the output as a video file (mp4 / webm / mov), or describes the work as a promo / spot / sting / reel / title sequence rather than a scrollable page. The canonical entry point is the /studio command, which loads this skill together with the design layer.
Related skills: motion-design-taste for the aesthetic brain; motion-state and motion-primitives for the default state workflow; motion-anti-slop Group G6 for the seek-contract checks; gsap-timeline and gsap-plugins (SplitText, MorphSVG, GSDevTools) for the API; motion-craft /studio for the command that orchestrates this skill.
Section 1 — The preview-project artifact
Every /studio run produces one folder, e.g. projects/cookware-promo/. The default path starts from state.json, then scripts/state-to-scene.mjs generates the choreography file. The shell files are stable scaffolding.
| File | Responsibility | Edit during tuning? |
|---|---|---|
state.json |
Default source of truth: duration, fps, layers, beats, primitive refs, assets. | Yes — default tuning surface |
index.html |
Static shell: fonts, --accent lock, .stage, #devtools mount, Export button, .js/.no-js gate, dev ?ar= preview, the GSDevTools-mount inline module. No choreography. |
Rarely (only fonts/accent/copy) |
scene.js |
Generated GSAP choreography. Exposes window.__studio = { gsap, tl, duration }. Wrapped in gsap.matchMedia. |
Generated artifact; escape-hatch edits require explicit choice |
render.mjs |
Node CLI: drives the timeline frame-by-frame in headless Chrome and encodes to video. Copied verbatim from the template. | Never |
package.json |
Declares puppeteer-core + @ffmpeg-installer/ffmpeg. Copied verbatim. |
Never |
What ships with it
9 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.
- 1mo ago First seen · 170 lines · 0 tokens per session scan A c85d09dcea87
motion-studio is a skill published in the GitHub repository taotao135791-bit/gsap-transform (2 stars, last pushed 3mo ago), licensed MIT. It adds 180 tokens to every session and 3,926 once invoked, about $0.0007 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…