copilot-mcp-server: Instructions file for Codex

AGENTS.md

copilot-mcp-server AGENTS.md is an instructions file for Codex, OpenCode from x51xxx/copilot-mcp-server. It costs 576 tokens per session, scanned A, original, MIT.

A repository-guidance document for copilot-mcp-server, a TypeScript server that provides tools to coding agents through the Model Context Protocol.

In plain words
What is it for?
Use it when adding or changing server tools, utilities, documentation, builds, lint checks, or development scripts.
Why use it?
It records the project’s structure, commands, coding conventions, and testing expectations so changes fit the repository.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is x51xxx/copilot-mcp-server's own configuration. It tells Codex and OpenCode how to work on copilot-mcp-server 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 copilot-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to x51xxx/copilot-mcp-server. 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/x51xxx/copilot-mcp-server/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/x51xxx/copilot-mcp-server

Made for: Codex, OpenCode.

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 copilot-mcp-server AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/x51xxx/copilot-mcp-server/agents-md.svg)](https://agentmods.dev/instructions/x51xxx/copilot-mcp-server/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/x51xxx/copilot-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/x51xxx/copilot-mcp-server/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 576 This file is loaded in full into every session.
When invoked 576 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00576 $0.00576
Opus 5 $0.00288 $0.00288
Sonnet 5 $0.00115 $0.00115
Haiku 4.5 $0.00058 $0.00058

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

Security

Grade A, and why

copilot-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 6d 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.

AGENTS.md · 43 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

  • src/ holds the MCP server entrypoint (index.ts), shared constants, and reusable utilities; tools live in src/tools/ and register through its local index.ts.
  • Place shared executors, parsers, and helpers in src/utils/ to avoid duplicating logic per tool.
  • docs/ runs the VitePress documentation site; update individual tool references in docs/api/tools/ when behaviour changes.
  • Build artifacts are emitted to dist/; support scripts sit under scripts/, and runnable samples stay in examples/ for quick demos.

Build, Test, and Development Commands

  • npm install installs dependencies (Node ≥ 18).
  • npm run build transpiles TypeScript to ESM code in dist/.
  • npm run dev rebuilds then boots the MCP server for iterative smoke tests.
  • npm start launches the already compiled server output.
  • npm run lint executes tsc --noEmit in strict mode; treat any failure as a blocker.
  • npm test currently passes as a placeholder—extend with targeted suites before relying on automation.
  • Docs workflows: npm run docs:dev, npm run docs:build, and npm run docs:preview for local authoring.

Coding Style & Naming Conventions

  • Use TypeScript with explicit types and Zod schemas for runtime validation.
  • Follow 2-space indentation, single quotes, and ESM imports ending in .js.
  • Name tools tool-name.tool.ts, export const toolNameTool, and register them in src/tools/index.ts.
  • Centralise shared behaviour in src/utils/ rather than copying logic across tools.

Testing Guidelines

  • Add focused test files beside the code under test (e.g. src/tools/ask.tool.test.ts).
  • Run npm run lint and npm run build before every PR to catch typing and compile issues.
  • Manually validate new tools via the GitHub Copilot CLI and confirm progress callbacks, error handling, and docs alignment.

Commit & Pull Request Guidelines

  • Use Conventional Commits (feat:, fix:, chore:) mirroring the existing history, and scope changes narrowly.
  • Document intent in each message, such as feat: add review prompt caching.
  • PRs should include a concise summary, linked issues, testing notes, relevant doc updates, and CLI output or screenshots for user-visible updates.

Read the full file on GitHub · 43 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. 6d ago First seen · 43 lines · 576 tokens per session scan A dec67fa12bd1

Subscribe to this mod's changes

copilot-mcp-server AGENTS.md is an instructions file published in the GitHub repository x51xxx/copilot-mcp-server (5 stars, last pushed 9mo ago), licensed MIT. It adds 576 tokens to every session, about $0.0029 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-31.

Related

Other instructions, from other repositories

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

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