gsap-transform: Instructions file for GitHub Copilot

.github/instructions/motion-state.instructions.md

gsap-transform motion-state.instructions.md is an instructions file for GitHub Copilot from taotao135791-bit/gsap-transform. It costs 236 tokens per session, scanned A, original, MIT.

A set of instructions for editing animation timelines through a structured state.json file instead of directly changing scene.js. It defines validation rules for timing, overlapping beats, schema version, and beat limits, then describes how to regenerate and render the scene.

In plain words
What is it for?
Use it when adding, moving, or changing beats and durations in a motion project that uses the motion-state runtime.
Why use it?
It keeps timeline changes validated and reproducible, reducing errors caused by editing generated scene code directly.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is taotao135791-bit/gsap-transform's own configuration. It tells GitHub Copilot how to work on gsap-transform itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gsap-transform configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/state-to-scene.mjs projects/{slug}.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/taotao135791-bit/gsap-transform/main/.github/instructions/motion-state.instructions.md
Clone the repo
git clone --depth 1 https://github.com/taotao135791-bit/gsap-transform

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for gsap-transform motion-state.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/taotao135791-bit/gsap-transform/motion-state.svg)](https://agentmods.dev/instructions/taotao135791-bit/gsap-transform/motion-state)
Your own site
<a href="https://agentmods.dev/instructions/taotao135791-bit/gsap-transform/motion-state"><img src="https://agentmods.dev/badge/instructions/taotao135791-bit/gsap-transform/motion-state.svg" alt="Measured on agentmods" height="20"></a>
Per session 236 This file is loaded in full into every session.
When invoked 236 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00236 $0.00236
Opus 5 $0.00118 $0.00118
Sonnet 5 $0.00047 $0.00047
Haiku 4.5 $0.00024 $0.00024

Measured 6d ago against content hash f0c7eada61a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

gsap-transform motion-state.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 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.

.github/instructions/motion-state.instructions.md · 26 lines

What it actually says

motion-state — state.json contract instructions

When the user asks the agent to edit a motion project's timeline (add a beat, change a duration, move something), the agent must operate on state.json — NOT on raw scene.js.

The state runtime is in skills/motion-state/runtime.mjs. Import it (Node) or read it from window.__studio (browser).

Every state mutation must call validate(state) before returning. Schema is in skills/motion-state/schema.json.

Group S anti-slop rules (all enforced by validate):

  • S1: at must be in [0, state.duration]
  • S2: two beats on the same layer cannot overlap unless allowOverlap: true
  • S4: schemaVersion: 1 is required
  • S5: total beats ≤ 200

After editing state.json, regenerate scene.js:

node scripts/state-to-scene.mjs projects/{slug}

Render from the project directory with node render.mjs --preset vertical or another supported preset.

Changes

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.

  1. 6d ago First seen · 26 lines · 236 tokens per session scan A f0c7eada61a2

Subscribe to this mod's changes

gsap-transform motion-state.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 236 tokens to every session, about $0.0012 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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens