Borrowing it
Nothing to install: this file belongs to dynamics365ninja/d365fo-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.
curl -O https://raw.githubusercontent.com/dynamics365ninja/d365fo-mcp-server/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/dynamics365ninja/d365fo-mcp-serverWrote 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/dynamics365ninja/d365fo-mcp-server/copilot-instructions)<a href="https://agentmods.dev/instructions/dynamics365ninja/d365fo-mcp-server/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/dynamics365ninja/d365fo-mcp-server/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.02316 | $0.02316 |
| Opus 5 | $0.01158 | $0.01158 |
| Sonnet 5 | $0.00463 | $0.00463 |
| Haiku 4.5 | $0.00232 | $0.00232 |
Grade A, and why
d365fo-mcp-server 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 7d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
D365 Finance & Operations X++ Development
Tool Priority
This workspace contains a D365FO MCP server. Always use the specialized MCP tools for D365FO objects (.xml, .xpp, .rnrproj, .label.txt). Built-in file/search tools are fine for .cs, .json, .yml, .md, .config files.
Mandatory First Check
Call get_workspace_info() before doing anything with D365FO objects.
| Response | Action |
|---|---|
| Call fails | STOP. MCP server not connected. Ask user to start it. |
⛔ CONFIGURATION PROBLEM |
STOP. Relay message. Wait for user. |
No ⛔ in the response |
Note the Model / Prefix lines. Proceed. |
Terminal Prohibition
PowerShell / any terminal command WILL HANG in VS 2022 / VS 2026 MCP integration. Never use run_in_terminal or generate scripts as a fallback when an MCP tool fails — STOP and report the error verbatim.
Core Tool Mapping
| Action | Tool |
|---|---|
| Plan an extension before changing code | prepare(mode="change", goal, objectName, methodName?) — returns signature, existing CoC wrappers, strategy + groundingToken |
| Plan a new object before creating it | prepare(mode="create", goal, objectName, objectType) — returns collision check, naming, EDT/label hints + groundingToken |
| Create a D365FO object | d365fo_file(action="create") (never create_file) |
| Edit an existing object | d365fo_file(action="modify") (applies immediately — confirm in chat first) |
| Revert the last write | d365fo_file(action="undo", filePath) — git-tracked → checkout HEAD (discards ALL uncommitted changes to that file); untracked → deleted |
| Search objects | search — multiple via search(queries[]), custom-only via search(scope="extensions") |
| Read any object's metadata | get_object_info(objectType, name, options?) — objectType ∈ class/table/form/query/view/enum/edt/report/data-entity/menu-item/service/map/config-key/security-policy/macro. 2+ known names: get_object_info(objects=[{objectType,objectName},…]) — ONE call, never a loop |
| Method signature for CoC | get_object_info(objectType="class", name, options={method, include:"signature"}) (already returned by prepare(mode="change")) |
| Validate X++ before write | validate_code(mode="syntax", code) — offline BP check, <50 ms |
| X++ rules & patterns | get_knowledge(kind="knowledge", topic) — select grammar, CoC, BP rules, SysOperation, workflow, … |
| Create a NEW form | object_patterns(domain="form", action="analyze", recommend={...}) → object_patterns(domain="form", action="spec", pattern) → generate_object(mode="scaffold", objectType="form", cloneFrom=referenceForm, tableMapping={...}) → object_patterns(domain="form", action="validate", xml) |
| Validate form XML against its pattern | object_patterns(domain="form", action="validate", xml | formName | filePath) — structural errors block form writes (FORM_PATTERN_ENFORCE) |
| Resolve label / EDT / class refs | validate_code(mode="references", code) |
| Build / BP / Sync | build_d365fo_project(bpCheck: true, dbSync: true) — ONE call compiles, runs the best-practice check and syncs AxDB |
| Error diagnosis | get_knowledge(kind="error", errorText) |
Parameters for a d365fo_file operation / generate_object mode |
get_knowledge(kind="op-spec", topic="add-index" | "table" | "scaffold:form") — those two tools keep their parameters OUT of the tool schema; look the contract up once for the operation you picked, then nest the values in params (properties for action="create") |
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.
- 7d ago First seen · 105 lines · 2,316 tokens per session scan A 658bcfa45b2b
d365fo-mcp-server copilot-instructions.md is an instructions file published in the GitHub repository dynamics365ninja/d365fo-mcp-server (138 stars, last pushed 2d ago), licensed MIT. It adds 2,316 tokens to every session, about $0.0116 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-30.
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.