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 umbraco/Umbraco-MCP-Base --skill releasegit clone --depth 1 https://github.com/umbraco/Umbraco-MCP-BaseWrote 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/umbraco/umbraco-mcp-base/release)<a href="https://agentmods.dev/skills/umbraco/umbraco-mcp-base/release"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/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/umbraco/umbraco-mcp-base/release"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco-mcp-base/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.00068 | $0.00884 |
| Opus 5 | $0.00034 | $0.00442 |
| Sonnet 5 | $0.00014 | $0.00177 |
| Haiku 4.5 | $0.00007 | $0.00088 |
Grade A, and why
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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Create a release branch from dev with version bumps and a structured changelog PR.
Arguments
The skill accepts an optional version argument (e.g., /release 17.1.2).
If no version is provided, read the current version from package.json and suggest the next patch version (increment the last number). Confirm with the user before proceeding.
Instructions
1. Pre-flight checks
Before anything else, verify the workspace is ready:
git fetch origin
git status # must be clean — warn and stop if uncommitted changes
git checkout dev
git pull
Check that dev is not behind main:
git log dev..origin/main --oneline
If main has commits not in dev, warn the user — they may need to merge main into dev first.
2. Determine the version
- If a version argument is provided, use it
- Otherwise, read
package.jsonversion, increment the patch number, and confirm with the user
3. Create the release branch
git checkout -b release/<version>
Branch naming convention: release/X.Y.Z (e.g., release/17.1.2)
4. Update version in these files
All files must be updated — the old version appears in each:
package.json— the"version"field (line 3)server.json— TWO version fields, both must match:- Top-level
"version"(around line 9) - Inside
packages[0].version(around line 14)
- Top-level
.claude-plugin/marketplace.json(if it exists) — THREE version fields:metadata.versionplugins[0].versionplugins[1].version(if present)
package-lock.json— runnpm install --package-lock-onlyto sync automatically
5. Build and verify
Run npm run build to confirm the project compiles cleanly. If it fails, fix the issue before continuing.
6. Commit the version bump
Commit message:
Bump version to <version>
7. Generate the changelog
Use git log to find all commits on dev since the last release merged to main:
git log origin/main..dev --oneline
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 · 125 lines · 68 tokens per session scan A 2952c627f7a9
release is a skill published in the GitHub repository umbraco/Umbraco-MCP-Base (2 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 884 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.