motion-mcp-server AGENTS.md

Repository instructions for Motion MCP Server, a program that connects AI assistants to Motion’s task-management service using the Model Context Protocol (MCP), a standard way for tools to communicate with AI applications.

In plain words
What is it for?
Use them when changing the TypeScript source, handlers, tools, services, schemas, or tests, including the optional Cloudflare Worker.
Why use it?
They explain the project layout, coding rules, build commands, and testing expectations so contributors can work consistently.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/markobullrush/motion-mcp-server/agents-md
Clone the repo
git clone --depth 1 https://github.com/markobullrush/motion-mcp-server

Made for: Codex, OpenCode.

Per session 621 This file is loaded in full into every session.
When invoked 621 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00621 $0.00621
Opus 5 $0.00311 $0.00311
Sonnet 5 $0.00124 $0.00124
Haiku 4.5 $0.00062 $0.00062

Measured yesterday against content hash 319391dd5d67, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

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.

AGENTS.md · 47 lines

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 source
    • handlers/ resource handlers (tasks, projects, users, etc.) implementing handle()
    • tools/ tool registry, configurator, and definitions
    • services/ Motion API client (motionApi.ts)
    • utils/ logging, validation, workspace resolution, caching, constants
    • schemas/ request/response schemas
    • types/ 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 to dist/
  • npm run mcp — run compiled server (dist/mcp-server.js)
  • npm run watch — incremental TypeScript compilation
  • npm 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, strict enabled (see tsconfig.json)
  • Indentation: 2 spaces; max 120 cols recommended
  • Quotes: prefer single quotes; match surrounding file if inconsistent
  • Naming: PascalCase classes/types; camelCase vars/functions; UPPER_SNAKE_CASE constants
  • Imports: absolute packages first, then relative modules; group by domain
  • Error handling: return MCP-friendly errors via formatMcpError; log with mcpLog

Testing Guidelines

  • Current: no test suite. At minimum run npm run type-check before PRs.
  • Suggested (future): vitest with files in src/**/__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-check passes, builds locally, no secrets committed
  • Keep changes focused; update docs if behavior or env changes (README.md, DEVELOPER.md).

Read the full file on GitHub · 47 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. yesterday First seen · 47 lines · 621 tokens per session scan A 319391dd5d67

Subscribe to this mod's changes

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.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 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,182 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,345 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

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.

vercel/next.js · 7,296 tokens