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/copilot-instructionsgit 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/copilot-instructions)<a href="https://agentmods.dev/instructions/mafzaal/d365fo-client/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/mafzaal/d365fo-client/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 | $0.01056 | $0.01056 |
| Opus 5 | $0.00528 | $0.00528 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
d365fo-client 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot instructions for d365fo-client
Build, test, and lint commands
Use uv for local commands and dependency management.
# install dependencies
uv sync --dev
# full test suite
uv run pytest
# unit tests only
uv run pytest tests/unit
# integration tests only
uv run pytest tests/integration
# run one test file
uv run pytest tests/unit/test_cli.py
# run one test case
uv run pytest tests/unit/test_cli.py::TestCLIManager::test_config_list_empty
# run one integration file directly
uv run pytest tests/integration/test_sandbox_crud.py
# run sandbox integration suite through the project runner
uv run python tests/integration/test_runner.py sandbox --verbose
# run one sandbox integration file through the runner
uv run python tests/integration/test_runner.py sandbox --test test_sandbox_crud.py
# formatting and linting
uv run black --check .
uv run isort --check-only .
uv run ruff check .
uv run mypy src/
# build
uv build
Cross-platform wrappers exist and mirror the same workflows:
- Unix:
make dev,make quality-check,make test-unit,make build - PowerShell:
.\make.ps1 dev,.\make.ps1 quality-check,.\make.ps1 test-unit,.\make.ps1 build
CI installs with uv sync --all-extras, runs uv run pytest tests/ --cov=src/ --cov-report=xml, and builds with uv build.
High-level architecture
This repo has three connected surfaces that share the same core client:
- Python client:
src/d365fo_client/client.pydefinesFOClient, which composes auth, HTTP session management, CRUD helpers, metadata API helpers, and label operations. Metadata is initialized lazily and uses the V2 cache/search/sync stack undersrc/d365fo_client/metadata_v2/. - CLI:
src/d365fo_client/main.pybuilds the argparse tree, andsrc/d365fo_client/cli.pyroutes commands throughCLIManager, which resolves config and then runs the sameFOClient. - MCP server:
src/d365fo_client/mcp/fastmcp_main.pyis the entry point,fastmcp_server.pyassembles the FastMCP server, and tool implementations live in mixins undersrc/d365fo_client/mcp/mixins/.D365FOClientManagerpoolsFOClientinstances per profile for MCP use.
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 · 79 lines · 1,056 tokens per session scan A 98e3ace80ace
d365fo-client copilot-instructions.md is an instructions file published in the GitHub repository mafzaal/d365fo-client (39 stars, last pushed 5d ago), licensed MIT. It adds 1,056 tokens to every session, about $0.0053 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
Claude Code 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.
Plonk AGENTS.md
AGENTS.md instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.