Borrowing it
Nothing to install: this file belongs to dave-palt/mcp-dynamics-365. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dave-palt/mcp-dynamics-365/master/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/dave-palt/mcp-dynamics-365Wrote 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/dave-palt/mcp-dynamics-365/copilot-instructions)<a href="https://agentmods.dev/instructions/dave-palt/mcp-dynamics-365/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/dave-palt/mcp-dynamics-365/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.02528 | $0.02528 |
| Opus 5 | $0.01264 | $0.01264 |
| Sonnet 5 | $0.00506 | $0.00506 |
| Haiku 4.5 | $0.00253 | $0.00253 |
Grade A, and why
mcp-dynamics-365 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 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.
How it starts
The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for MCP Dynamics 365 Server
This file contains specific instructions for AI assistants working on this codebase.
Project Overview
This is a Model Context Protocol (MCP) server for Microsoft Dynamics 365 CRM. It provides AI agents with tools to perform CRUD operations, query data, fetch schemas, and execute custom operations on Dynamics 365 entities.
🚨 Critical: Stay Current with MCP Technology
The Model Context Protocol ecosystem is rapidly evolving - changes occur weekly or even daily. Before working on any MCP-related features:
📚 ALWAYS Check Latest Documentation First
-
Read the official MCP SDK documentation: Use the
fetch_webpagetool to check the latest changes at:- Main documentation: https://modelcontextprotocol.io/
- SDK GitHub: https://github.com/modelcontextprotocol/typescript-sdk
- Release notes and changelog for breaking changes
- API documentation for current interfaces and patterns
-
Check for deprecations and new features:
- Transport implementations (HTTP, stdio, SSE)
- Client/server interfaces and lifecycle methods
- Tool definition schemas and parameter handling
- Authentication and security patterns
-
Verify current best practices:
- Package imports and module structure
- Error handling patterns
- Type definitions and interfaces
- Transport configuration and setup
⚠️ Common Pitfalls to Avoid
- Don't assume existing patterns are current - always verify against latest docs
- Don't use deprecated transport methods - HTTP/SSE implementations change frequently
- Don't skip version checking - MCP SDK updates often include breaking changes
- Don't implement without research - newer, simpler approaches may be available
🔄 When to Re-check Documentation
- Before implementing any new MCP features
- When encountering transport or connection issues
- When SDK version updates are available
- When error patterns don't match current documentation
- Before troubleshooting connectivity or protocol issues
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.
- 6d ago First seen · 305 lines · 2,528 tokens per session scan A 03b5fdbd4c56
mcp-dynamics-365 copilot-instructions.md is an instructions file published in the GitHub repository dave-palt/mcp-dynamics-365 (2 stars, last pushed 6mo ago), licensed MIT. It adds 2,528 tokens to every session, about $0.0126 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
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.
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 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).
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).
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.
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.