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/azure-samples/remote-mcp-functions-dotnet/copilot-instructionsgit clone --depth 1 https://github.com/Azure-Samples/remote-mcp-functions-dotnetWrote 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/azure-samples/remote-mcp-functions-dotnet/copilot-instructions)<a href="https://agentmods.dev/instructions/azure-samples/remote-mcp-functions-dotnet/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/azure-samples/remote-mcp-functions-dotnet/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.00329 | $0.00329 |
| Opus 5 | $0.00164 | $0.00164 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
remote-mcp-functions-dotnet 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.
What it actually says
You are an ai assistant tasked assisting the developer to build and deploy MCP Servers successfully using Azure Functions. Our ultimate goal is for the user to be able to complete this quickstart guide, where the app is deployed and healthy in azure, and the MCP client tools are calling this MCP server.
Here are some specific requirements and pieces of context:
- This must build a working Azure Function project complete with code, Readme changes, and AZD bicep. The original repo is already in this state, so your job is to preserve it.
- If I ever ask you to run a tool (e.g. say hello, save snippet or get snippet), prompt to run the MCP tool (which will use mcp.json) and never try to get me to rerun this project or a process to run the tool first.
- AZD and the func (aka Azure Functions Core Tools) commandline tools are the main tools to be used for deployment, provisioning and running locally. As soon as the user has done the
azd uporazd provisionstep at least once, you can learn all values of their azure application like resource group and function app name using the environment variables stored in the .azure folder. Please proactively use these and be helpful to suggest running commands for the developer, replacing placeholder values when possible with these environment variables. - This particular project is dotnet-isolated (.NET 10) Azure Function in C#
- We prefer using Azure Functions bindings if they can work versus the Azure SDKs, but Azure SDKs are ok if there is no substitute.
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 · 10 lines · 329 tokens per session scan A e47fb094faf7
remote-mcp-functions-dotnet copilot-instructions.md is an instructions file published in the GitHub repository Azure-Samples/remote-mcp-functions-dotnet (133 stars, last pushed 23d ago), licensed MIT. It adds 329 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.