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/ccampora/mcp_xpp/copilot-instructionsgit clone --depth 1 https://github.com/ccampora/mcp_xppWrote 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/ccampora/mcp_xpp/copilot-instructions)<a href="https://agentmods.dev/instructions/ccampora/mcp_xpp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/ccampora/mcp_xpp/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.00313 | $0.00313 |
| Opus 5 | $0.00156 | $0.00156 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
mcp_xpp 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 4d 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.
What it actually says
Golden Rules:
- DO NOT use Emojis in the code
- If you are creating test suites or adhoc test file, use the clients provided in the tests/tools folder
- You will use the Build and Run Task only, do not attempt to build differentely
- Avoid hardcoding. If you need to hardcode, you MUST ask first
- Any adhoc tests, misc files, outputs, and/or anything that should not be versioned, put it in the misc folder.
- Internal documentation must be place in docs/internal folder.
D365 Object Creation: 7. Before creating D365 objects (tables, entities, enums, forms) via MCP tools, ALWAYS read the creation recipes in docs/internal/d365-creation-recipes/ first. These contain proven parameter sets, required defaults, and known pitfalls.
- docs/internal/d365-creation-recipes/README.md - Index and overview
- docs/internal/d365-creation-recipes/table-field-defaults.md - Required default params per field type
- docs/internal/d365-creation-recipes/table-creation.md - Table creation recipe
- docs/internal/d365-creation-recipes/data-entity-with-staging.md - Data entity + staging table recipe
- docs/internal/d365-creation-recipes/common-property-gotchas.md - Known pitfalls and solutions
- When you discover new required parameters, patterns, or gotchas during D365 object creation, update the relevant recipe file immediately so the knowledge is not lost.
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.
- 4d ago First seen · 16 lines · 313 tokens per session scan A ca3da4f35a43
mcp_xpp copilot-instructions.md is an instructions file published in the GitHub repository ccampora/mcp_xpp (40 stars, last pushed 2mo ago), licensed MIT. It adds 313 tokens to every session, about $0.0016 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.