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.
git clone --depth 1 https://github.com/VuDZ/RoslynMcpServerWrote 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/rules/vudz/roslynmcpserver/roslyn-mcp-dev-conventions)<a href="https://agentmods.dev/rules/vudz/roslynmcpserver/roslyn-mcp-dev-conventions"><img src="https://agentmods.dev/badge/rules/vudz/roslynmcpserver/roslyn-mcp-dev-conventions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/vudz/roslynmcpserver/roslyn-mcp-dev-conventions"><img src="https://agentmods.dev/badge/rules/vudz/roslynmcpserver/roslyn-mcp-dev-conventions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00251 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
roslyn-mcp-dev-conventions 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.
What it actually says
Tools & Services changes
- Register new tools in
McpToolCatalog(names, host, group, lite-core, read/write). That catalog drives DI host registration and method-level MCP SDK registration. Do not add a parallelWithTools<T>()list. - Constructor-inject
SolutionManager/ helpers; tools are singletons. - Resolve all relative file paths via
ResolvePathAgainstWorkspace. - Prefer structured return strings (markdown sections,
###metadata) matching existing tools. - Log outcomes as summary + warning highlights; gate full dumps behind
ROSLYN_MCP_LOG_TOOL_OUTPUT=full. - Friendly errors for bad/missing args — avoid unhandled exceptions leaking as opaque MCP failures.
- Add/adjust unit tests under
RoslynMcpServer.Testsfor parsers, resolvers, path helpers. - Version: follow always-apply rule
roslyn-mcp-version-bump.mdc— patch-bump after successful self-build when shipping code/tool changes; sync README +AGENTS.md.sample.
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 · 17 lines · 0 tokens per session scan A a5802a1a5d53
roslyn-mcp-dev-conventions is a cursor rule published in the GitHub repository VuDZ/RoslynMcpServer (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 251 tokens. 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-09-14.
Other cursor rules, from other repositories
dotnet-testing
.NET-specific testing standards for ASP.NET Core applications. Covers test naming, project structure, unit and integration testing patterns, builders, Testcontainers, and WebApplicationFactory. Complements engineering-principles.mdc and dotnet-architecture.mdc.
jest-unit-testing-cursorrules-prompt-file
Cursor rules for Jest development with unit testing.
python-cursorrules-prompt-file-best-practices
Cursor rules for Python development with best practices integration.
go
Idiomatic Go rules. Explicit error handling, interface-based design, context-first concurrency.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.
csharp
C# / .NET coding standards (Frontier).