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.
npx skills add Byggarepop/dotnet-mcp-orchestrator --skill publish-releasegit clone --depth 1 https://github.com/Byggarepop/dotnet-mcp-orchestratorWrote 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/byggarepop/dotnet-mcp-orchestrator/publish-release)<a href="https://agentmods.dev/skills/byggarepop/dotnet-mcp-orchestrator/publish-release"><img src="https://agentmods.dev/badge/skills/byggarepop/dotnet-mcp-orchestrator/publish-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/byggarepop/dotnet-mcp-orchestrator/publish-release"><img src="https://agentmods.dev/badge/skills/byggarepop/dotnet-mcp-orchestrator/publish-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.00063 | $0.00755 |
| Opus 5 | $0.00032 | $0.00378 |
| Sonnet 5 | $0.00013 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
publish-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 12d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publishing a McpOrchestrator release
The release is tag-driven: a vX.Y.Z tag on main triggers release.yml, which builds and
tests on three OSes, produces Native-AOT binaries, creates the GitHub Release, publishes to
NuGet (trusted publishing), and updates the MCP Registry listing. Your job is only to get the
version bump onto main and push the tag.
Preconditions — check before touching anything
CHANGELOG.mdhas a## [Unreleased]section that actually describes the changes being released. Feature PRs are supposed to write their entries there; if it is missing or empty, STOP and write it first (fromgit log <last-tag>..main) — the release notes are extracted from this section, matched to the tag.mainis green (the merged PRs passed CI) and your checkout is clean.- Pick the version by semver against the
[Unreleased]content: breaking → major, feature → minor, fixes only → patch.
Step 1 — the bump PR (exactly two files)
git checkout main && git pull
git checkout -b bump-X.Y.Z
McpOrchestrator/McpOrchestrator.csproj:<Version>→X.Y.Z.CHANGELOG.md: rename## [Unreleased]→## [X.Y.Z] - <today's date>.- Nothing else. Do NOT use
git add -A(it sweeps untracked local files in); add the two files by name. Commit message:Bump version to X.Y.Z— no setup instructions, noClaude-Session:trailer (Co-Authored-By:is fine).
Open the PR and squash-merge it. Branch protection requires a review, so the merge needs the admin override — get the user's explicit go-ahead, then:
gh pr merge <n> --squash --delete-branch --admin
Step 2 — tag and deploy
Tag only a commit that is on main, never a branch:
git checkout main && git pull # must now contain the bump commit
git tag vX.Y.Z && git push origin vX.Y.Z
The tag push starts the release workflow (~8 minutes). Watch it:
gh run list --limit 1
gh run watch <run-id> --exit-status
Step 3 — verify
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 72 lines · 63 tokens per session scan A 036a449da552
publish-release is a skill published in the GitHub repository Byggarepop/dotnet-mcp-orchestrator (2 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 755 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-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…