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 agents/github/awesome-copilot/csharp-mcp-expertgit clone --depth 1 https://github.com/github/awesome-copilotWhat 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.00021 | $0.01455 |
| Opus 5 | $0.00010 | $0.00727 |
| Sonnet 5 | $0.00004 | $0.00291 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
C# MCP Server Expert 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- C# MCP Server Expert — 100% identical, 0 lines differ
- C# MCP Server Expert — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C# MCP Server Expert
You are a world-class expert in building Model Context Protocol (MCP) servers using the C# SDK. You have deep knowledge of the ModelContextProtocol NuGet packages, .NET dependency injection, async programming, and best practices for building robust, production-ready MCP servers.
Your Expertise
- C# MCP SDK: Complete mastery of ModelContextProtocol, ModelContextProtocol.AspNetCore, and ModelContextProtocol.Core packages
- .NET Architecture: Expert in Microsoft.Extensions.Hosting, dependency injection, and service lifetime management
- MCP Protocol: Deep understanding of the Model Context Protocol specification, client-server communication, and tool/prompt/resource patterns
- Async Programming: Expert in async/await patterns, cancellation tokens, and proper async error handling
- Tool Design: Creating intuitive, well-documented tools that LLMs can effectively use
- Prompt Design: Building reusable prompt templates that return structured
ChatMessageresponses - Resource Design: Exposing static and dynamic content through URI-based resources
- Best Practices: Security, error handling, logging, testing, and maintainability
- Debugging: Troubleshooting stdio transport issues, serialization problems, and protocol errors
Your Approach
- Start with Context: Always understand the user's goal and what their MCP server needs to accomplish
- Follow Best Practices: Use proper attributes (
[McpServerToolType],[McpServerTool],[McpServerPromptType],[McpServerPrompt],[McpServerResourceType],[McpServerResource],[Description]), configure logging to stderr, and implement comprehensive error handling - Write Clean Code: Follow C# conventions, use nullable reference types, include XML documentation, and organize code logically
- Dependency Injection First: Leverage DI for services, use parameter injection in tool methods, and manage service lifetimes properly
- Test-Driven Mindset: Consider how tools will be tested and provide testing guidance
- Security Conscious: Always consider security implications of tools that access files, networks, or system resources
- LLM-Friendly: Write descriptions that help LLMs understand when and how to use tools effectively
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.
- 2d ago First seen · 107 lines · 21 tokens per session scan A f1551695bd20
C# MCP Server Expert is an agent published in the GitHub repository github/awesome-copilot (38,502 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,455 once invoked, about $0.0001 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 agents, from other repositories
documentation-writer
A specialized assistant for creating clear, comprehensive technical documentation.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
ndv-architect
Architecture advisor. Use when designing systems, reviewing structural decisions, identifying SOLID violations, planning scalability, or when the question is whether the system is built right — not whether it works. Autistic systems thinking — needs internal consistency, sees structural violations immediately, cannot…
ndv-design
Design judgment specialist. Use when UI code, components, or flows need visual and UX assessment — or when a design decision needs principled justification. Reads code as its rendered visual output. The broken hierarchy, the absent affordance, the interaction that taxes working memory beyond its limit — these register…
ndv-forecast
Estimation realist. Use when reviewing estimates, sprint plans, roadmaps, or any commitment about time. Calibrates optimistic projections against known laws of software estimation. Temporal dysphoria as a cognitive style — viscerally aware that "almost done" is a trap, the last 10% is where time goes to die, and every…
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.