Borrowing it
Nothing to install: this file belongs to taotao135791-bit/gsap-transform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/taotao135791-bit/gsap-transform/main/AGENTS.mdgit 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/instructions/taotao135791-bit/gsap-transform/agents-md)<a href="https://agentmods.dev/instructions/taotao135791-bit/gsap-transform/agents-md"><img src="https://agentmods.dev/badge/instructions/taotao135791-bit/gsap-transform/agents-md.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.01296 | $0.01296 |
| Opus 5 | $0.00648 | $0.00648 |
| Sonnet 5 | $0.00259 | $0.00259 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
gsap-transform AGENTS.md 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 8d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSAP Transform — Hard Rules for AI Coding Agents
This file is the source of truth for coding agents using this repository.
Claude Code and Gemini import it through CLAUDE.md and GEMINI.md.
GSAP Transform is a third-party, community, agent-oriented GSAP motion skill system. It is not an official GreenSock or Webflow project.
Before changing or generating motion, read skills/llms.txt.
Product Path
Always traverse the three-layer system in this order:
- Design Layer — decide motion taste before code.
skills/motion-design-taste/skills/motion-anti-slop/skills/video-grammar/when the artifact is video-like
- State Layer — edit the motion timeline as data.
skills/motion-state/skills/motion-primitives/templates/{slug}/state.json
- API Layer — use GSAP implementation details only after direction and
state are clear.
skills/gsap-core/skills/gsap-timeline/skills/gsap-scrolltrigger/skills/gsap-plugins/skills/gsap-react/skills/gsap-frameworks/skills/gsap-performance/
Default workflow:
Brief / product context
-> Design Read
-> motion dials
-> state.json edits
-> primitives
-> generated scene
-> preview/render
-> anti-slop check
Design Read
Before writing GSAP code, output one line:
Reading this as: {page kind} for {audience}, with a {vibe} language, leaning toward {aesthetic family} and {motion language}.
Then pick a motion mode:
- Restrained
- Expressive
- Cinematic
Let duration, ease, and stagger inherit from the selected mode.
State Is The Default Source
state.jsonis the default source of truth.scene.js/scene.mjsare generated artifacts.- Do not hand-edit generated
scene.jsas the normal agent workflow. - After editing
state.json, regenerate:
node scripts/state-to-scene.mjs projects/{slug}
Hand-written scenes are allowed only as an explicit escape hatch for advanced users or historical examples.
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.
- 8d ago First seen · 165 lines · 1,296 tokens per session scan A 28adc5cd3ee1
gsap-transform AGENTS.md is an instructions file published in the GitHub repository taotao135791-bit/gsap-transform (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,296 tokens to every session, about $0.0065 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.