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/mafzaal/d365fo-client/agents-mdgit clone --depth 1 https://github.com/mafzaal/d365fo-clientWrote 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/mafzaal/d365fo-client/agents-md)<a href="https://agentmods.dev/instructions/mafzaal/d365fo-client/agents-md"><img src="https://agentmods.dev/badge/instructions/mafzaal/d365fo-client/agents-md.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 | $0.03256 | $0.03256 |
| Opus 5 | $0.01628 | $0.01628 |
| Sonnet 5 | $0.00651 | $0.00651 |
| Haiku 4.5 | $0.00326 | $0.00326 |
Grade A, and why
d365fo-client 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 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 — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guide for D365FO MCP Server
This guide is specifically designed for AI agents and assistants to effectively interact with Microsoft Dynamics 365 Finance & Operations through the d365fo-client MCP server. It provides structured workflows, best practices, and common patterns for successful automation and integration.
Architecture Overview
The d365fo-client MCP server provides 49 comprehensive tools organized across 9 functional categories, implemented using a modern FastMCP mixin-based architecture for enhanced performance and maintainability. All tools are available through standardized MCP protocol interactions regardless of the underlying implementation.
Quick Start for AI Agents
Essential First Steps
- Test Connectivity: Always start with
d365fo_test_connectionto verify environment access - Get Environment Info: Use
d365fo_get_environment_infoto understand the D365FO environment capabilities - Explore Available Entities: Use
d365fo_search_entitiesto discover relevant data entities for your tasks
// Step 1: Test connection
{
"tool": "d365fo_test_connection",
"arguments": {}
}
// Step 2: Get environment information
{
"tool": "d365fo_get_environment_info",
"arguments": {}
}
// Step 3: Search for relevant entities
{
"tool": "d365fo_search_entities",
"arguments": {
"pattern": "customer",
"limit": 10
}
}
Core Workflows for AI Agents
1. Data Discovery and Exploration
Use Case: Understanding available data structures and relationships
// Discover entities by business area
{
"tool": "d365fo_search_entities",
"arguments": {
"pattern": "sales|customer|invoice",
"category": "Master",
"limit": 20
}
}
// Get detailed schema for specific entity
{
"tool": "d365fo_get_entity_schema",
"arguments": {
"entityName": "CustomersV3",
"includeProperties": true,
"includeKeys": true,
"resolveLabels": true
}
}
// Search for related actions
{
"tool": "d365fo_search_actions",
"arguments": {
"pattern": "customer",
"limit": 10
}
}
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 · 535 lines · 3,256 tokens per session scan A f962c0d1e00f
d365fo-client AGENTS.md is an instructions file published in the GitHub repository mafzaal/d365fo-client (39 stars, last pushed 4d ago), licensed MIT. It adds 3,256 tokens to every session, about $0.0163 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
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
ai-toolkit AGENTS.md
AGENTS.md instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).
flyto-core CLAUDE.md
Claude Code instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
cyxj-groksearch CLAUDE.md
Claude Code instructions for chenyuxiaojin/cyxj-groksearch, covering claude.md, 常用命令 and 结构与坑.