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/ivanmurzak/mcp-plugin-dotnet/copilot-instructionsgit clone --depth 1 https://github.com/IvanMurzak/MCP-Plugin-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/ivanmurzak/mcp-plugin-dotnet/copilot-instructions)<a href="https://agentmods.dev/instructions/ivanmurzak/mcp-plugin-dotnet/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/ivanmurzak/mcp-plugin-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.00604 | $0.00604 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
MCP-Plugin-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 3d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Guidelines
Code Style
- Namespaces: Use Java-style reverse domain namespaces (e.g.,
com.IvanMurzak.McpPlugin). This is mandatory and overrides standard C# conventions. - File Headers: ALL C# files MUST start with the specific ASCII art header containing author, repo, and license info. Copy an existing header exactly.
- Formatting:
- Use Allman style (braces on new lines).
_camelCasefor private fields.PascalCasefor public members.
- Reactive Programming: Prefer
R3(Reactive Extensions) for event handling (Subject<Unit>,Observable<T>). - Data Inspection: Use
com.IvanMurzak.ReflectorNetfor runtime metadata inspection over standard Reflection where applicable. - Logging: Use
Microsoft.Extensions.Configurationabstractions backed by NLog.
Architecture
- Core Library (
McpPlugin): ImplementsMcpToolManager,McpResourceManager,McpPromptManager. - Server Integration (
McpPlugin.Server): ASP.NET Core integration.- Register:
builder.Services.WithMcpServer(...) - Middleware:
app.UseMcpPluginServer(...)
- Register:
- Common (
McpPlugin.Common): Shared utilities likeIDisposableAsyncandVersioninfo. - Transports: Supports
stdio(local process) andstreamableHttp(SSE/HTTP).
Build and Test
- Build:
dotnet build McpPlugin.sln - Test:
dotnet test(RunsMcpPlugin.TestsandMcpPlugin.Server.Tests)- Testing uses xUnit, Shouldly, and Moq.
- Automation: Check
commands/for PowerShell scripts (e.g.,bump-version.ps1,update-reflectornet.ps1).
Project Conventions
- CLI Arguments: Use
DataArgumentsclass for parsing command-line arguments and transport settings, not justIConfiguration. - Disposal: Implement
IDisposableAsyncfor asynchronous cleanup resources. - Attributes: Heavy use of attributes for tool definitions (from
ReflectorNetor internal MCP attributes).
Integration Points
- ASP.NET Core: See
DemoWebAppfor reference implementation. UseIDependencyInjectionto resolve services. - Console Apps: See
DemoConsoleAppforstdiotransport examples. - SignalR: Used internally in
McpPlugin.Serverfor some communication aspects.
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.
- 3d ago First seen · 47 lines · 604 tokens per session scan A a82a16a545ae
MCP-Plugin-dotnet copilot-instructions.md is an instructions file published in the GitHub repository IvanMurzak/MCP-Plugin-dotnet (20 stars, last pushed 4d ago), licensed Apache-2.0. It adds 604 tokens to every session, about $0.0030 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
Connapse CLAUDE.md
Instructions for Destrayon/Connapse, covering claude.md, build & run, build, run web app (requires backing services) and full stack via docker.
collattice CLAUDE.md
Instructions for MrBildo/collattice, covering collattice, repository rules — hard, tech stack, build & run and prerequisites.
GameDev-MCP-Server CLAUDE.md
Instructions for IvanMurzak/GameDev-MCP-Server, covering claude.md, what this is, build / run and versioning / releases.
WPFVisualTreeMcp CLAUDE.md
Instructions for faze79/WPFVisualTreeMcp, covering claude.md, project overview, build commands, build solution and build for release.
kioku AGENTS.md
AGENTS.md instructions for sandovaldavid/kioku, covering kioku agent operating manual, repository scope, source-of-truth order, current verified snapshot and branch and pull-request workflow.
fieldcure-mcp-rag CLAUDE.md
Claude Code instructions for fieldcure/fieldcure-mcp-rag, covering claude.md, what this is, build & test commands, build and run all tests (185 tests, mstest).