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-version-bump)<a href="https://agentmods.dev/rules/vudz/roslynmcpserver/roslyn-mcp-version-bump"><img src="https://agentmods.dev/badge/rules/vudz/roslynmcpserver/roslyn-mcp-version-bump/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-version-bump"><img src="https://agentmods.dev/badge/rules/vudz/roslynmcpserver/roslyn-mcp-version-bump.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.00514 | $0.00514 |
| Opus 5 | $0.00257 | $0.00257 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
roslyn-mcp-version-bump 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
Auto version bump (this MCP server)
When changing RoslynMcpServer itself and verifying with this same MCP (build/test/run via MCP tools, then use the new binary):
When to bump
After a successful run_dotnet_build / dotnet test (and before or with dotnet publish + MCP reload):
- Bump patch in
RoslynMcpServer.csproj:Version,AssemblyVersion,FileVersiontogether (e.g.1.0.14→1.0.15,1.0.14.0→1.0.15.0). - Do not leave shippable behavior changes at the old version — agents check
get_mcp_server_infoagainst the number in csproj/docs. - Skip bump only for pure docs/typos/rules with no code or tool-behavior change.
SemVer in this repo
- Patch (
1.0.x): fixes, tool UX, parsers, path resolve, logging — default for almost every ship. - Minor (
1.x.0): new MCP tools or clearly additive public capabilities. - Do not bump
PackageVersion(0.1.0-beta) unless packaging intentionally changes.
After bump
- Update README «Agent tools by version» (+ RU pointer) when user-visible tools/behavior change.
- Sync
AGENTS.md.sample/ expected version hints (get_mcp_server_info→ new version). - Publish (
publish-and-verify.ps1ordotnet publish … -r win-x64), reload MCP host, confirmget_mcp_server_infoshows the new version.
Dogfooding
Prefer MCP run_dotnet_build / run_dotnet_test / run_dotnet_run on this repo’s workspace — same as app repos. Shell dotnet only if MCP is unavailable or for publish/reload scripts that are outside tool coverage.
publish-and-verify.ps1 stops leftover RoslynMcpServer.exe under this repo/publish (Cursor often keeps MCP alive after disconnect and locks publish DLLs). Pass -SkipKill to disable. Then reload MCP and confirm get_mcp_server_info.
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 · 35 lines · 514 tokens per session scan A caf2ed622efe
roslyn-mcp-version-bump is a cursor rule published in the GitHub repository VuDZ/RoslynMcpServer (7 stars, last pushed yesterday), licensed MIT. It adds 514 tokens to every session, about $0.0026 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-09-14.
Other cursor rules, from other repositories
fusebase-flow-implementation
Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.
007-commit-conventions
APPLY commit message conventions WHEN creating commits TO ensure clear and consistent version history.
hook-commits
Set up pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
pytest-integration-tests
Below is an example test. Notice the following.
git
Git workflow and commit conventions.
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.