Borrowing it
Nothing to install: this file belongs to darylmcd/Roslyn-Backed-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/darylmcd/Roslyn-Backed-MCP/main/.claude/skills/release-cut/SKILL.mdgit clone --depth 1 https://github.com/darylmcd/Roslyn-Backed-MCPWrote 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/skills/darylmcd/roslyn-backed-mcp/release-cut)<a href="https://agentmods.dev/skills/darylmcd/roslyn-backed-mcp/release-cut"><img src="https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/release-cut/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/skills/darylmcd/roslyn-backed-mcp/release-cut"><img src="https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/release-cut.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.00058 | $0.04964 |
| Opus 5 | $0.00029 | $0.02482 |
| Sonnet 5 | $0.00012 | $0.00993 |
| Haiku 4.5 | $0.00006 | $0.00496 |
Grade A, and why
release-cut 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 6d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Cut
You are a release engineer running the full release pipeline as a single atomic flow. Sequence the release phases (bump -> verify -> ship -> tag -> refresh-plugin) with shared error handling and checkpointed step output, so a mid-flow failure re-runs from the last successful checkpoint rather than restarting from the top.
The server ships on two install surfaces and Step 6 refreshes both:
| Layer | Surface | Refreshed by |
|---|---|---|
| Layer 1 | standalone global .NET tool darylmcd.roslynmcp (command roslynmcp) |
just tool-update |
| Layer 2 | Claude Code plugin — marketplace cache, skills, hooks, exact-version dnx pin |
maintainer-local /update skill |
Neither layer is optional. They drift apart silently and in both directions: v1.29.0 and v1.34.2 updated Layer 1 and left Layer 2 stale in the plugin cache; v4.1.2 refreshed Layer 2 and left Layer 1 a release behind because the global-tool update was documented as optional. eng/verify-install-layers.ps1 is the check that closes Step 6 — a release is not refreshed until it exits 0.
Input
The $ARGUMENTS parameter is the bump type: patch, minor, or major. If not provided, ask the user which type of bump to perform with a brief explanation:
- patch (1.27.0 -> 1.27.1): bug fixes, doc changes, no new features
- minor (1.27.0 -> 1.28.0): new features, new stable tools, backward-compatible changes
- major (1.27.0 -> 2.0.0): breaking changes to stable tool contracts
Refusal conditions (check these FIRST, before any action)
Refuse and report cleanly — do NOT produce a partial release — if any of the following hold:
- Working tree has uncommitted changes (
git status --porcelainnon-empty). Message: "Refusing: working tree must be clean before a release cut. Commit or stash first." - Current branch is not
main. Message: "Refusing: release cuts run from main. Current branch: ." mainis not up-to-date withorigin/main(aftergit fetch). Message: "Refusing: local main is behind origin/main. Run git pull --ff-only first."$ARGUMENTSis not one ofpatch/minor/major. Message: "Refusing: bump type must be 'patch', 'minor', or 'major'. Got: ."pwsh -NoProfile -File eng/verify-surface-snapshot-freshness.ps1exits non-zero. Message: "Refusing: the .ai-doc-audit.md Live Surface snapshot has drifted from the live surface. Run /surface-audit, refresh the table, and re-date the heading first." The script prints the per-row delta; re-measure rather than hand-editing the numbers to green.
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.
- 6d ago Changed · +67 lines 2044e2748faf
- 10d ago First seen · 228 lines · 58 tokens per session scan A 40f123b76d64
release-cut is a skill published in the GitHub repository darylmcd/Roslyn-Backed-MCP (1 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 4,964 once invoked, about $0.0003 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-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.