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/ryan-yang125/motion-lexicon/agents-mdgit clone --depth 1 https://github.com/Ryan-yang125/motion-lexiconWrote 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/ryan-yang125/motion-lexicon/agents-md)<a href="https://agentmods.dev/instructions/ryan-yang125/motion-lexicon/agents-md"><img src="https://agentmods.dev/badge/instructions/ryan-yang125/motion-lexicon/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.00876 | $0.00876 |
| Opus 5 | $0.00438 | $0.00438 |
| Sonnet 5 | $0.00175 | $0.00175 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
motion-lexicon 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Operating Context
This repository is Motion Lexicon, a static React + TypeScript product for visual animation vocabulary.
Use these files as the current project context:
README.md: project overview, commands, routes, SEO model, and delivery status.PRODUCT.md: product promise, user model, phase strategy, and quality bar.DESIGN.md: launch architecture, visual system, URL state, and acceptance criteria.prototype/motion-lexicon-prototype.html: archived phase-one reference; current production styling lives insrc/styles.cssandsrc/library.css.
Communication
- Write Chinese by default.
- Use direct positive phrasing. Avoid先否定再转折的表达方式。
- Be concrete about files, commands, routes, and verification results.
Product Boundary
- Keep this as a static frontend application unless the user adds a server-side requirement.
- Store content, assets, categories, recipes, and i18n data on the frontend.
- Preserve the V6 component-library system: a quiet chroma-zero shell, expressive Product Mono, Editorial Warm, and Spatial Dark scenes, black primary actions, a restrained blue state color, thin borders, compact radii, small mono metadata, dominant preview canvases, and dense documentation structure.
- Keep the product workflow centered on browsing motion, previewing behavior, tuning parameters, copying prompt/code, and reading review guidance.
- Treat React as the site implementation. User-facing exports are portable Prompt, HTML, CSS, and framework-independent JavaScript where interaction requires it.
- Keep the V6 release contract at exactly 100 Components across 11 categories and 10 Page Blocks. Preserve 44 canonical Primitives and all 91 source terms through canonical mappings and redirects; the Motion Lexicon Skill remains independently versioned at 4.2.0.
Technical Stack
- Vite, React, TypeScript.
- Tailwind CSS v4 plus the project stylesheet in
src/styles.css. - Local shadcn-style UI components backed by Radix primitives.
- lucide-react icons.
- TanStack Router.
- i18next and react-i18next.
- react-helmet-async for route metadata.
- Build-time static prerendering through
src/entry-server.tsxandscripts/prerender.ts. - Vitest and Playwright for verification.
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.
- 4d ago First seen · 84 lines · 876 tokens per session scan A 0b638c7ffe89
motion-lexicon AGENTS.md is an instructions file published in the GitHub repository Ryan-yang125/motion-lexicon (41 stars, last pushed today), licensed MIT. It adds 876 tokens to every session, about $0.0044 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-anything AGENTS.md
AGENTS.md instructions for nexu-io/motion-anything, covering agents.md — working agreement for any ai agent on this repo, what this project is, repository map, the recipe manifest schema (recipe.motion.yaml) and ── 分类五维（建库标准，取值见下方 §"分类标准") ─────────────────────────.
motion-anything CLAUDE.md
Claude Code instructions for nexu-io/motion-anything, covering claude.md and claude-specific notes.
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).
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.
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.
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.