Borrowing it
Nothing to install: this file belongs to VuDZ/RoslynMcpServer. 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/VuDZ/RoslynMcpServer/main/.cursor/skills/prepare-github-release/SKILL.mdgit 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/skills/vudz/roslynmcpserver/prepare-github-release)<a href="https://agentmods.dev/skills/vudz/roslynmcpserver/prepare-github-release"><img src="https://agentmods.dev/badge/skills/vudz/roslynmcpserver/prepare-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/skills/vudz/roslynmcpserver/prepare-github-release"><img src="https://agentmods.dev/badge/skills/vudz/roslynmcpserver/prepare-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.00086 | $0.00547 |
| Opus 5.5 | $0.00034 | $0.00219 |
| Sonnet 5.5 | $0.00017 | $0.00109 |
| Haiku 4.5 | $0.00009 | $0.00055 |
Grade A, and why
prepare-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 1mo 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
Prepare GitHub Release
The agent cannot authenticate git push (SSH key passphrase). Do not tag,
push, or run gh release create. Actions creates the tag and Release after a
human workflow_dispatch.
When to run
Only when the user explicitly asked to release. Never after a normal merge, bugfix, or docs commit.
| User says | -CommitRef |
|---|---|
| выпусти / текущий / HEAD | HEAD (default) |
| предыдущий / прошлый коммит | HEAD~1 |
| SHA | that SHA |
Steps
- Read this skill. Run from the repo root (PowerShell; use
;not&&):
powershell -NoProfile -File .github/scripts/Get-ReleaseMetadata.ps1 -CommitRef HEAD
Pass -Strict after the commit is already on origin/main and the change is not docs-only.
-
Stop if the script throws or reports:
- On origin/main : False — user must
git pushthat commit themselves, then dispatch. - Docs-only : True — refuse a binary release (README in the zip is not a reason).
- Tag
v{Version}would collide with an already shipped version — they need a csproj bump first.
- On origin/main : False — user must
-
Reply with SHA,
v{Version}, notes preview, and:GitHub → Actions → Release → Run workflow
- Branch:
main commit_sha: the SHA from the script
Workflow URL is in the script output (
run_workflow_url). - Branch:
-
Do not create a local tag. Actions will create
v{Version}on that SHA.
Notes
- Changelog: commit subjects (and bodies) since the previous
v*tag; newest 16 if there are more. - Batch bugfixes: wait until the last commit is on
main, then dispatch that SHA once. force=trueon the workflow is only for an intentional docs-only binary republish.
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.
- 1mo ago First seen · 58 lines · 86 tokens per session scan A e57f540a6a79
prepare-github-release is a skill published in the GitHub repository VuDZ/RoslynMcpServer (8 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 547 once invoked, about $0.0003 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 skills, from other repositories
safe-github-push
A workflow for safely pushing Git repositories that contain large assets or binary files to GitHub. It checks repository changes and file sizes before planning commits and pushes.
git-onboarding-auto
A Git setup and pull-request workflow automation skill. Git is the version-control tool developers use to track code changes, while a pull request is a request for teammates to review and merge those changes.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
draft-release
Draft a new release of the project.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.