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/ritchy-eu/teams-mcp/copilot-instructionsgit clone --depth 1 https://github.com/Ritchy-EU/teams-mcpWrote 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/ritchy-eu/teams-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/ritchy-eu/teams-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/ritchy-eu/teams-mcp/copilot-instructions.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.1 | $0.01097 | $0.01097 |
| Opus 5 | $0.00549 | $0.00549 |
| Sonnet 5 | $0.00219 | $0.00219 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
teams-mcp copilot-instructions.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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — teams-mcp
Architecture
This is an MCP (Model Context Protocol) server that bridges AI assistants to Microsoft Graph APIs for Teams, chats, users, and search. It runs as a CLI tool (npx @ritchy-eu/teams-mcp@latest) over stdio transport.
Key components
src/index.ts— Entry point. Dual-mode: CLI commands (authenticate,check,logout) and MCP server mode (default). Registers all tool modules against a singleMcpServerinstance.src/services/graph.ts—GraphServicesingleton. Manages Microsoft Graph client initialization from a stored OAuth token (~/.msgraph-mcp-auth.json). All Graph API calls flow throughgraphService.getClient().src/tools/*.ts— Tool registration modules (auth,chats,search,teams,users). Each exports aregister*Tools(server, graphService)function that callsserver.tool()with Zod schemas for input validation.src/types/graph.ts— Re-exports@microsoft/microsoft-graph-typesand defines custom response/summary interfaces (GraphApiResponse<T>,*Summarytypes). All API response shapes live here.src/utils/— Shared helpers:markdown.ts(markdown→sanitized HTML via marked+DOMPurify),attachments.ts(image hosted content uploads),users.ts(@mention parsing and user lookup).
Data flow
AI Assistant → stdio → McpServer → register*Tools handler → GraphService.getClient() → Microsoft Graph API
Development
npm run build # Clean + tsc compile
npm run dev # Watch mode (node --watch)
npm test # vitest run
npm run test:watch # vitest interactive
npm run test:coverage # vitest with v8 coverage (80% threshold on all metrics)
npm run lint # biome check
npm run lint:fix # biome check --write --unsafe
TypeScript & Module Conventions
- ESM-only (
"type": "module"in package.json). Use.jsextensions in import paths (TypeScriptmoduleResolution: "bundler"). - Strict mode enabled with
noUnusedLocals,noUnusedParameters,exactOptionalPropertyTypes,noImplicitOverride. - Prefix unused catch variables with underscore:
catch (_error). - Linting/formatting via Biome (not ESLint/Prettier). Use
node:protocol for Node.js built-in imports.
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.
- 5d ago First seen · 78 lines · 1,097 tokens per session scan A eb0d814ed2d0
teams-mcp copilot-instructions.md is an instructions file published in the GitHub repository Ritchy-EU/teams-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 1,097 tokens to every session, about $0.0055 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.
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).
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.
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).
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.
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.
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.