Borrowing it
Nothing to install: this file belongs to Odrin/rhizome-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/Odrin/rhizome-mcp/main/.github/skills/rhizome-release/SKILL.mdgit clone --depth 1 https://github.com/Odrin/rhizome-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/odrin/rhizome-mcp/rhizome-release)<a href="https://agentmods.dev/skills/odrin/rhizome-mcp/rhizome-release"><img src="https://agentmods.dev/badge/skills/odrin/rhizome-mcp/rhizome-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/odrin/rhizome-mcp/rhizome-release"><img src="https://agentmods.dev/badge/skills/odrin/rhizome-mcp/rhizome-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.00103 | $0.01288 |
| Opus 5.5 | $0.00041 | $0.00515 |
| Sonnet 5.5 | $0.00021 | $0.00258 |
| Haiku 4.5 | $0.00010 | $0.00129 |
Grade A, and why
rhizome-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 16d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rhizome release
Releases are published from main. Publishing a GitHub release creates the tag and fires .github/workflows/release.yml (release: published), which builds binaries and publishes npm, the MCP Registry, the VS Code Marketplace, and Open VSX. Do not push tags by hand and do not stamp versions in files: the workflow stamps server.json, the VS Code extension version, and (afterwards, on main) plugins/rhizome-mcp/.claude-plugin/plugin.json.
Track the release as a rhizome-mcp issue like any other work (see the rhizome-task-workflow skill): create a task titled Publish vX.Y.Z release with the distribution label, claim it with CHANGELOG.md as a reserved file resource, save a checkpoint after verification, and finish_attempt with the commit, release URL, and workflow run URL as artifacts.
1. Scope the release
git pull && git status --short --branch # must be clean and not behind
git tag --sort=-version:refname | head -3 # previous tag
git log --oneline v<prev>..HEAD # full range
git log --format='%h %s' v<prev>..HEAD | rg -v 'Update (unit|integration) coverage badge|stamp plugin manifest'
Ignore generated badge and plugin-stamp commits. Read the diffs of consequential commits (git show --no-ext-diff --unified=8 <sha>) instead of trusting subjects. Confirm the new tag and release do not exist yet:
git ls-remote --exit-code origin refs/tags/vX.Y.Z # must fail
gh release view vX.Y.Z --repo Odrin/rhizome-mcp # must fail
Pick the version: breaking contract change = major, new capability = minor, fixes/internal only = patch.
2. Write the CHANGELOG entry
Insert ## [X.Y.Z] - YYYY-MM-DD (today) directly above the previous release in CHANGELOG.md. Follow Keep a Changelog sections in this order: Added, Changed, Fixed, Removed, Internal; omit empty ones.
- One bullet per behavior, not per commit:
- **Bold summary** — what changed, who is affected, observable effect and error codes.Group related commits (e.g. severalperf(...)commits become one bullet). - Describe shipped behavior verified in the diff, not commit-message intent. Name tools, commands, flags, and error codes in backticks.
- Release-pipeline, CI, test-only, and coverage changes go under
Internal.
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.
- 16d ago First seen · 80 lines · 103 tokens per session scan A 88463bbe872c
rhizome-release is a skill published in the GitHub repository Odrin/rhizome-mcp (1 stars, last pushed 16d ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,288 once invoked, about $0.0004 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-10-14.
Other skills, from other repositories
release
Publish a herdr-gpui release. Use when the user asks to cut, push, ship, or publish a release, or to approve, verify, or GPG-sign one that is already running. Covers just release, the protected environments the run stops at, and the local verification and signing steps that are not part of CI.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
repo-sentinel
Full security audit for public repositories across 12 attack surfaces: git history, secrets, CI/CD, containers, dependencies, licenses. Triggers on: "push to GitHub", "make repo public", "open source this", "is this safe to push", "release audit", "secret leaks".
ship-workflow
Resumable shipping lifecycle: reconciles current Git and GitHub facts from any entry (dirty default or feature branch, local commits, published branch, open PR, existing manual or native stack, merged work), commits dirty work as lossless logical commits, publishes or reuses the PR, requires current CI and review…
ci-cd-pipeline-authoring
Use when a repository needs CI/CD - author GitHub Actions workflows so TaskTrooper's pipeline auto-detects your validate/build/test jobs and stage/preprod/prod deploys, and so a dispatch delivery profile can dispatch the production deploy.
release-playbook
Use when you need the end-to-end merge -> deploy -> watch -> verdict sequence for a delivery mode, or a tool result you did not expect (refusal, park, tag exists).