motionworks: Instructions file for Claude Code

CLAUDE.md

motionworks CLAUDE.md is an instructions file for Claude Code from jhn-kim/motionworks. It costs 471 tokens per session, scanned C, a copy of motionworks AGENTS.md, MIT.

Project instructions for coding agents working in the MotionWorks codebase. They specify which documentation to read and how to handle conflicts between code and the documented rules.

In plain words
What is it for?
Preparing for coding tasks, locating architecture and data-contract guidance, and following rules for schemas and coordination between agents.
Why use it?
They help agents understand the project before changing it and avoid silently changing unclear or outdated documentation.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is jhn-kim/motionworks's own configuration. It tells Claude Code how to work on motionworks 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 motionworks configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jhn-kim/motionworks. 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/jhn-kim/motionworks/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/jhn-kim/motionworks

Made for: Claude Code.

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 motionworks CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jhn-kim/motionworks/claude-md/github.svg)](https://agentmods.dev/instructions/jhn-kim/motionworks/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/jhn-kim/motionworks/claude-md"><img src="https://agentmods.dev/badge/instructions/jhn-kim/motionworks/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for motionworks CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jhn-kim/motionworks/claude-md"><img src="https://agentmods.dev/badge/instructions/jhn-kim/motionworks/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 471 This file is loaded in full into every session.
When invoked 471 The same file — it is already loaded in full.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00471 $0.00471
Opus 5 $0.00235 $0.00235
Sonnet 5 $0.00094 $0.00094
Haiku 4.5 $0.00047 $0.00047

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

Security

Grade C, and why

motionworks CLAUDE.md scanned grade C with 1 finding 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- motionworks-instructions-start -->
Origin

This is a copy

100% identical to motionworks AGENTS.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 27 lines

How it starts

The opening of the file, as written. The whole thing — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions

Before you start

Read docs/OVERVIEW.md first — it orients you to the project with no prior context assumed. Then read whichever of the following apply to your task:

  • docs/ARCHITECTURE.md — system structure and design decisions
  • docs/SCHEMA.md — data contracts and schema definitions
  • docs/AGENT_INTEGRATION.md — how agents interface with the system
  • docs/RUNTIME_BRIDGE.md — runtime coordination between agents
  • docs/OVERLAY.md — overlay layer design
  • docs/MANIPULATION_SURFACES.md — surfaces agents can act on
  • docs/SOURCE_SYNC.md — source-of-truth sync behavior
  • docs/CHALLENGES.md — known risks and how they're mitigated

Rules

  • Any task involving schema, data contracts, or agent-to-agent coordination requires reading SCHEMA.md and AGENT_INTEGRATION.md in full first. Do not infer the contract from code alone.
  • These docs are the source of truth. If you find a task in conflict with what's documented, treat the doc as authoritative unless the human operator tells you otherwise.
  • If a doc is wrong, outdated, or incomplete: do not edit it silently. Propose the specific change and wait for confirmation before writing.

This project uses MotionWorks for motion design. Before you implement or refine motion, read MOTIONWORKS.md — it defines the CSS-variable contract, overlay setup, and journal writeback rules. Setup (npx motionworks init) is a one-time human step; if MOTIONWORKS.md already exists it is done — do not re-run it, just read that guide and start the daemon. Whenever you scaffold or mount motion — or run/serve the app so the designer can view or refine its motion — start the daemon yourself in the background first (npx motionworks from the project root) and confirm it with npx motionworks status before you report the work done; the overlay is inert until it runs. Before editing motion values, run npx motionworks changes and process entries oldest first.

Read the full file on GitHub · 27 lines

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. 8d ago First seen · 27 lines · 471 tokens per session scan C ac464c11b5ae

Subscribe to this mod's changes

motionworks CLAUDE.md is an instructions file published in the GitHub repository jhn-kim/motionworks (0 stars, last pushed 11d ago), licensed MIT. It adds 471 tokens to every session, about $0.0024 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). It is 100% identical to motionworks AGENTS.md, differing in 2 lines, and is treated as a copy.

Related

Other instructions, from other repositories

vibetags com-example-config-AsyncTestConfig.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.

PIsberg/vibetags · 82 tokens

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,153 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