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/gsap-core)<a href="https://agentmods.dev/rules/taotao135791-bit/gsap-transform/gsap-core"><img src="https://agentmods.dev/badge/rules/taotao135791-bit/gsap-transform/gsap-core.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.00000 | $0.00395 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
gsap-core 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 6d 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
gsap-core
When you write GSAP code, use these conventions:
- Imports:
import { gsap } from "gsap". All plugins free since Webflow acquisition; no Club /.npmrc/ auth token needed. - Sequencing:
gsap.timeline()with position parameter ("+=0.5","<", labels). Avoid chaineddelay. - Transforms: prefer GSAP aliases (
x,y,scale,rotation,xPercent,yPercent) over raw CSStransformor layout (top,left,width). - Opacity: prefer
autoAlphaoveropacity(also setsvisibility). gsap.from(autoAlpha:0)on a CSS-hidden element animates 0 → 0 (no motion). Usegsap.fromTo()with explicit start state.- Multiple
from()/fromTo()on the same property of the same element: setimmediateRender: falseon later ones. - Wrap every project in
gsap.matchMedia()with at least(prefers-reduced-motion: no-preference)and(prefers-reduced-motion: reduce)branches — paint end state in the reduced branch.
Pair with motion-design-taste for aesthetic direction before implementing.
For full reference: skills/gsap-core/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.
- 6d ago First seen · 22 lines · 0 tokens per session scan A d0f20fac09f5
gsap-core is a cursor rule published in the GitHub repository taotao135791-bit/gsap-transform (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 395 tokens. 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
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.