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.
git 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-recipes)<a href="https://agentmods.dev/rules/taotao135791-bit/gsap-transform/motion-recipes"><img src="https://agentmods.dev/badge/rules/taotao135791-bit/gsap-transform/motion-recipes.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.1 | $0.00072 | $0.00333 |
| Opus 5 | $0.00036 | $0.00167 |
| Sonnet 5 | $0.00014 | $0.00067 |
| Haiku 4.5 | $0.00007 | $0.00033 |
Grade A, and why
motion-recipes 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 7d 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-recipes
Eight clone-able aesthetic × motion combos. Each ships:
- recommended dial values (
MOTION_INTENSITY/DESIGN_VARIANCE/VISUAL_DENSITY) - typography pool and color rule
- layout pattern
- motion language (durations, eases, stagger band)
- a GSAP code skeleton
Recipes:
- Editorial Kinetic — kinetic typography + SplitText + restrained parallax
- Brutalist Scroll — heavy type + pinned scrub + Flip grid
- Liquid Glass Hover — dark + glass cards + magnetic CTA
- Bento Flip — non-uniform tiles + ScrollTrigger.batch + Flip
- Minimal Fade — autoAlpha + small y, no scrub/pin
- Cinematic Pinned Scrub — full-screen pin + multi-layer parallax + SplitText + MorphSVG
- Kinetic Type Stagger — type fills viewport + char stagger + expo.out
- Grid Break Overlap — asymmetric grid + element overlap + differential y
For all eight skeletons, see skills/motion-recipes/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.
- 7d ago First seen · 27 lines · 72 tokens per session scan A 6bcca536bbd1
motion-recipes is a cursor rule published in the GitHub repository taotao135791-bit/gsap-transform (2 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 333 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
design-engine
End-to-end AI design system with 190+ styles, AI photo generation, and pixel-perfect export. Use when designing posters, carousels, thumbnails, PDFs, websites, or any visual content.
slide-styling-guidelines
Cursor rule "slide-styling-guidelines" from darrenhinde/slidev-ai-presenations, covering slidev presentation guidelines for interns, preventing content overflow & creating professional slides, text content rules, mermaid diagram guidelines and code slide guidelines.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.