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/markobullrush/motion-mcp-server/claude-mdgit clone --depth 1 https://github.com/markobullrush/motion-mcp-serverWrote 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/markobullrush/motion-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/markobullrush/motion-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/markobullrush/motion-mcp-server/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 | $0.01328 | $0.01328 |
| Opus 5 | $0.00664 | $0.00664 |
| Sonnet 5 | $0.00266 | $0.00266 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
motion-mcp-server 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 2d 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.
This is a copy
100% identical to motion-mcp-server CLAUDE.md — 0 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Motion MCP Server
MCP server bridging Motion's task management API with LLMs via the Model Context Protocol. Supports both local (stdio) and remote (Cloudflare Workers) deployment.
Common Commands
# Build & Run
npm run build # Compile TypeScript to dist/
npm run mcp # Start MCP server (compiled)
npm run mcp:dev # Start MCP server (ts-node, no build needed)
npm run type-check # Type checking without emitting files
# Testing (vitest)
npm test # Run all unit tests
npm test -- handlers.task # Run a single test file by name fragment
npm test -- --reporter=verbose # Run with verbose output
npm run test:integration # Integration tests (requires MOTION_API_KEY in .env)
# Worker (Cloudflare)
npm run worker:dev # Local Worker at http://localhost:8787
npm run worker:deploy # Deploy to Cloudflare
npm run worker:type-check # Type-check Worker code (separate tsconfig)
# Verify both entry points compile
npm run build && npm run worker:type-check
# Quick startup smoke test
timeout 3s npm run mcp
Testing
Uses vitest. Unit tests in tests/**/*.spec.ts, integration tests in tests/integration/**/*.integration.test.ts.
- Unit tests: 10s timeout, mocked services,
tests/setup.tssilences console.error - Integration tests: 60s timeout, sequential execution (rate limits), requires
MOTION_API_KEYenv var - Handler tests mock
MotionApiServiceandWorkspaceResolver; service returns useListResult<T>shape ({ items, truncation })
Architecture
Entry Points
Both share all handlers, services, tools, and utilities — they differ only in transport and API key source.
- Stdio Server (
src/mcp-server.ts): UsesServerfrom MCP SDK. API key fromMOTION_API_KEYenv var. - Cloudflare Worker (
src/worker.ts): UsesMcpAgentfrom Cloudflare Agents SDK with Durable Objects. API key from Worker secret. Auth via secret token in URL path (/mcp/SECRET).
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.
- 2d ago First seen · 118 lines · 1,328 tokens per session scan A f0b08c717d21
motion-mcp-server CLAUDE.md is an instructions file published in the GitHub repository markobullrush/motion-mcp-server (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,328 tokens to every session, about $0.0066 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to motion-mcp-server CLAUDE.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.