Borrowing it
Nothing to install: this file belongs to nexu-io/motion-anything. 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/nexu-io/motion-anything/main/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/nexu-io/motion-anything/claude-md"><img src="https://agentmods.dev/badge/instructions/nexu-io/motion-anything/claude-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.00261 | $0.00261 |
| Opus 5 | $0.00130 | $0.00130 |
| Sonnet 5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
motion-anything CLAUDE.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.
What it actually says
CLAUDE.md
This project follows a single, tool-agnostic working agreement so it can be continued by any AI agent in any session.
👉 Read AGENTS.md first — it is the source of truth for repo structure,
the recipe manifest schema, the golden path for adding recipes, and the hard rules.
👉 Then read PROGRESS.md — current status and the task queue.
👉 The motion standard is MOTION-SPEC.md — every recipe and the router
skill must obey it.
Claude-specific notes
- This repo is intentionally plain files (Markdown / YAML / HTML / CSS / JS) with no build step, so the user can switch tools or resume in a fresh session at any time without losing context. Keep it that way.
- When the user describes a motion in natural language, your job is the loop in
skills/motion-anything/SKILL.md: classify intent → pick recipes fromrecipes/honoringMOTION-SPEC.md(especially the restraint budget) → produce the output. - Prefer extending the library and the spec over one-off code. The reusable recipe is the asset.
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 · 23 lines · 261 tokens per session scan A f8006a1ec264
motion-anything CLAUDE.md is an instructions file published in the GitHub repository nexu-io/motion-anything (762 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 261 tokens to every session, about $0.0013 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
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).
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.
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.
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).
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.