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-github-release)<a href="https://agentmods.dev/rules/vudz/roslynmcpserver/roslyn-mcp-github-release"><img src="https://agentmods.dev/badge/rules/vudz/roslynmcpserver/roslyn-mcp-github-release/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-github-release"><img src="https://agentmods.dev/badge/rules/vudz/roslynmcpserver/roslyn-mcp-github-release.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.00304 | $0.00304 |
| Opus 5.5 | $0.00122 | $0.00122 |
| Sonnet 5.5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
roslyn-mcp-github-release 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 24d 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
GitHub Releases (this repo)
Do not git tag, git push, or gh release create for a product release.
The agent cannot unlock the SSH key. Tag + GitHub Release are created by
.github/workflows/release.yml after a human Actions → Release → Run workflow.
When the user asks to выпусти релиз / пометь релизным / cut a GitHub Release:
read .cursor/skills/prepare-github-release/SKILL.md and run
.github/scripts/Get-ReleaseMetadata.ps1. Do not invent a second release path.
Skip a binary release for docs/rules-only trees. Local version bumps stay independent of GitHub Releases (several bugfixes may share one dispatch).
CI shards (AnalyzerLifecycle vs unit, remainder filter): .cursor/rules/roslyn-mcp-ci.mdc.
Do not replace test-suite.yml with one sequential dotnet test.
Attest Release zips only (actions/attest-build-provenance on publish after
New-PublishZip, before gh release create). Do not attest CI TRX. Job
publish needs id-token: write and attestations: write in addition to
contents: write. This is provenance, not Authenticode.
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.
- 24d ago First seen · 26 lines · 304 tokens per session scan A 5a1c52e3ee1c
roslyn-mcp-github-release is a cursor rule published in the GitHub repository VuDZ/RoslynMcpServer (8 stars, last pushed 8d ago), licensed MIT. It adds 304 tokens to every session, about $0.0012 per session on Opus 5.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-22.
Other cursor rules, from other repositories
publishing-dotnettool
This file serves as a guideline for the Cursor AI Agent to ensure the proper creation, packaging, and publishing of a dotnet tool. Follow these rules to maintain consistency, quality, and security across published tools.
release
PULSE Release Process - Checklist for publishing updates.
releasing
How to release AdLoop to PyPI — version bumping, tagging, and publishing.
05-release-preparation
Prepare a semver release (CHANGELOG, pyproject.toml, uv.lock, checks).
release
Changesets release pipeline - version PR and its dispatched CI check, shared vX.Y.Z tag, CI gate before tagging, release:check gate, Dependabot changesets, no npm publish, GITHUBTOKEN tag trigger limitation.
cd
GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, cf workers versions create then a 100% deployment in deployOrder, scoped API token on the production environment, GitHub-owned deployment record.