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/.github/instructions/motion-craft.instructions.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/motion-craft)<a href="https://agentmods.dev/instructions/taotao135791-bit/gsap-transform/motion-craft"><img src="https://agentmods.dev/badge/instructions/taotao135791-bit/gsap-transform/motion-craft.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.00488 | $0.00488 |
| Opus 5 | $0.00244 | $0.00244 |
| Sonnet 5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
gsap-transform motion-craft.instructions.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 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-craft — command workflow instructions
When the user invokes a slash command in the /motion-craft <subcommand> family, follow that command's exact Sequence and Output contract from skills/motion-craft/SKILL.md. State the affected scope before working ("Working on the hero section only" / "Working across all sections").
| Command | Trigger phrases | Output |
|---|---|---|
/motion-craft init |
"set up motion for this project" | MOTION.md brief at project root + Design Read |
/motion-craft shape |
"plan motion before coding", "storyboard this" | beat list + selected recipe + dial values |
/motion-craft animate |
"implement the animations" | GSAP code conforming to recipe and motion mode |
/motion-craft polish |
"polish this", "final pass" | tightened durations / eases / staggers + reduced-motion branch |
/motion-craft audit |
"audit", "lint", "remove the slop" | structured report from motion-anti-slop |
/motion-craft critique |
"design review" | qualitative review (does motion serve content?) |
/motion-craft quieter |
"tone this down" | one-step reduction along Restrained → Expressive → Cinematic |
/motion-craft bolder |
"amplify", "boring" | one-step amplification with discipline |
/motion-craft adapt |
"make it accessible", "responsive" | gsap.matchMedia + breakpoint-aware motion |
/motion-craft export |
"export as transparent video", "render to webm" | capture.js (Puppeteer) + FFmpeg commands |
Universal conventions (see skills/motion-craft/SKILL.md):
- Every command begins by reading project state: existing GSAP imports, tween count, ScrollTrigger count, presence of
gsap.matchMedia. - Every command ending in code MUST run an internal pass against
motion-anti-slopblock-severity rules before returning. - Never ask multi-question dumps; if a clarifier is needed, exactly ONE question.
Composable: init → shape → animate → polish → audit.
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 · 28 lines · 488 tokens per session scan A eb90f7679ac4
gsap-transform motion-craft.instructions.md is an instructions file published in the GitHub repository taotao135791-bit/gsap-transform (2 stars, last pushed 2mo ago), licensed MIT. It adds 488 tokens to every session, about $0.0024 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.