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.
npx agentmods add instructions/nexu-io/motion-anything/agents-mdgit clone --depth 1 https://github.com/nexu-io/motion-anythingWrote 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/nexu-io/motion-anything/agents-md)<a href="https://agentmods.dev/instructions/nexu-io/motion-anything/agents-md"><img src="https://agentmods.dev/badge/instructions/nexu-io/motion-anything/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 | $0.02195 | $0.02195 |
| Opus 5 | $0.01097 | $0.01097 |
| Sonnet 5 | $0.00439 | $0.00439 |
| Haiku 4.5 | $0.00219 | $0.00219 |
Grade A, and why
motion-anything 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 5d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — working agreement for any AI agent on this repo
This file is the single source of truth for any coding agent (Claude Code, Cursor, Codex,
Aider, …) working on motion-anything. If you are an AI picking this project up cold, read this
file and PROGRESS.md first — they are designed so the project can be continued by any tool, in
any new session, without losing context.
What this project is
motion-anything is an open-source, chat-native motion engine: a curated + standardized
library of motion recipes, a "taste engine" (MOTION-SPEC.md), and a router skill that turns one
sentence of intent into produced, tasteful animation. It is an independent product that shares
resources with and interlocks with Open Design:
every recipe is authored as an Open-Design-compatible SKILL.md so it can drop straight into
OD's skills/ and bind to OD design systems' motion section.
Read the product thesis in README.md. Read live status and the task queue in PROGRESS.md.
Repository map
| Path | Role |
|---|---|
recipes/<surface>/<recipe-id>/ |
One motion recipe. Surfaces: web/, interaction/, video/. |
recipes/<...>/recipe.motion.yaml |
Machine manifest (gallery + router read this). Schema below. |
recipes/<...>/SKILL.md |
The portable, Open-Design-compatible skill for this recipe. |
recipes/<...>/preview.html |
Self-contained, openable live demo. No build step, no external deps. |
recipes/<...>/*.css, *.js, *.jsx |
The reusable implementation(s). |
skills/motion-anything/SKILL.md |
The router meta-skill: intent → classify → pick → produce. |
MOTION-SPEC.md |
The motion standard. Every recipe and the router MUST obey it. |
gallery/index.html |
The possibility gallery (static; reads recipes). |
cli/ |
Minimal Node CLI: list, add <recipe>, gallery. |
The recipe manifest schema (recipe.motion.yaml)
Mirrors Open Design / html-video manifests, extended with the three fields that make this product
unique (intent_keywords, avoid_when, restraint).
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.
- 5d ago First seen · 140 lines · 2,195 tokens per session scan A fd5dbc9e20a7
motion-anything AGENTS.md is an instructions file published in the GitHub repository nexu-io/motion-anything (756 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,195 tokens to every session, about $0.0110 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-30.
Other instructions, from other repositories
motion-lexicon AGENTS.md
AGENTS.md instructions for Ryan-yang125/motion-lexicon, covering agent instructions, operating context, communication, product boundary and technical stack.
motionworks AGENTS.md
AGENTS.md instructions for jhn-kim/motionworks, covering agent instructions, before you start and rules.
motionworks CLAUDE.md
Claude Code instructions for jhn-kim/motionworks, covering agent instructions, before you start and rules.
excalimate CLAUDE.md
Instructions for excalimate/excalimate, covering excalimate, component library, icons and coding conventions.
svg-animation-studio CLAUDE.md
Instructions for ChanMeng666/svg-animation-studio, covering claude.md — repository map & api index, 1. what this repo is, 2. directory map, 3. lib api index and 4. workflow (the natural-language loop).
remotion-bits AGENTS.md
AGENTS.md instructions for av/remotion-bits, covering task execution, debugging methodology, coding guidelines, documenting your work and development.