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 rules/taotao135791-bit/gsap-transform/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/rules/taotao135791-bit/gsap-transform/motion-studio)<a href="https://agentmods.dev/rules/taotao135791-bit/gsap-transform/motion-studio"><img src="https://agentmods.dev/badge/rules/taotao135791-bit/gsap-transform/motion-studio.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.00089 | $0.00490 |
| Opus 5 | $0.00044 | $0.00245 |
| Sonnet 5 | $0.00018 | $0.00098 |
| Haiku 4.5 | $0.00009 | $0.00049 |
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 4d 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
motion-studio
Produces a self-contained preview project (projects/{slug}/): state.json + generated scene.js + index.html + render.mjs + serve.mjs + package.json. Preview with node serve.mjs (timeline UI via GSDevTools), render with node render.mjs --preset vertical or another supported preset.
Default tuning path: edit state.json, run node scripts/state-to-scene.mjs projects/{slug}, then refresh. Hand-written scene.js is an escape hatch, not the normal agent workflow.
Seek contract (enforced by motion-anti-slop Group G6):
- expose
window.__studio = { gsap, tl, duration }and dispatch__studio:ready; - gate
GSDevTools.create()on!window.__RENDERING; - default-import every plugin from esm.sh — including GSDevTools (G4/G6.3);
- gate
SplitTextondocument.fonts.ready(G6.5); - keep the scene time-driven (no
ScrollTrigger scrub, noquickTo/pointer tweens).
Seek method: tl.time(t) per frame — NOT gsap.updateRoot(). A timeline built inside gsap.matchMedia() is NOT on gsap.globalTimeline, so updateRoot cannot drive it. Four gotchas are baked into render.mjs: file:// CORS (→ local http server), matchMedia seek (→ tl.time), tl-object serialization timeout (→ block-body evaluate that returns undefined), headless rAF (→ host-side setTimeout).
For the full contract, gotchas, recipe allowlist, and tuning loop: see skills/motion-studio/SKILL.md.
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.
- 4d ago First seen · 23 lines · 89 tokens per session scan A 8129db612f6f
motion-studio is a cursor rule published in the GitHub repository taotao135791-bit/gsap-transform (2 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 490 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.