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/agents-mdgit clone --depth 1 https://github.com/markobullrush/motion-mcp-serverWhat 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.00621 | $0.00621 |
| Opus 5 | $0.00311 | $0.00311 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
motion-mcp-server 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 yesterday.
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 MotionMCP AGENTS.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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/— TypeScript sourcehandlers/resource handlers (tasks, projects, users, etc.) implementinghandle()tools/tool registry, configurator, and definitionsservices/Motion API client (motionApi.ts)utils/logging, validation, workspace resolution, caching, constantsschemas/request/response schemastypes/shared TypeScript types
dist/— compiled JS output.env.example— copy to.env; never commit secrets- Entry point:
src/mcp-server.ts(stdio MCP server)
Build, Test, and Development Commands
npm run mcp:dev— run server via ts-node (fast dev)npm run build— compile TypeScript todist/npm run mcp— run compiled server (dist/mcp-server.js)npm run watch— incremental TypeScript compilationnpm run type-check— strict type/unused checks (no emit)- Optional (Cloudflare worker):
npm run worker:dev,npm run worker:deploy
Coding Style & Naming Conventions
- Language: TypeScript,
strictenabled (seetsconfig.json) - Indentation: 2 spaces; max 120 cols recommended
- Quotes: prefer single quotes; match surrounding file if inconsistent
- Naming:
PascalCaseclasses/types;camelCasevars/functions;UPPER_SNAKE_CASEconstants - Imports: absolute packages first, then relative modules; group by domain
- Error handling: return MCP-friendly errors via
formatMcpError; log withmcpLog
Testing Guidelines
- Current: no test suite. At minimum run
npm run type-checkbefore PRs. - Suggested (future):
vitestwith files insrc/**/__tests__and coverage >80% for changed lines.
Commit & Pull Request Guidelines
- Commits: Conventional Commits (e.g.,
feat(tools): add consolidated tasks,fix(handlers): null-safe workspace) - PRs must include:
- Clear description and rationale; reference issues (e.g.,
Closes #123) - Before/after behavior or example tool calls/args
- Checklist:
type-checkpasses, builds locally, no secrets committed
- Clear description and rationale; reference issues (e.g.,
- Keep changes focused; update docs if behavior or env changes (
README.md,DEVELOPER.md).
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.
- yesterday First seen · 47 lines · 621 tokens per session scan A 319391dd5d67
motion-mcp-server AGENTS.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 621 tokens to every session, about $0.0031 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to MotionMCP AGENTS.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.