ToolHive is a platform for running and managing Model Context Protocol servers, which give AI clients access to tools and data. Developers, platform teams, and enterprises use it to isolate MCP servers, control access, and monitor their operation. The catalogue entries provide agent workflows and configuration for operating ToolHive and its MCP servers.
Borrowing it
Nothing to install: this file belongs to stacklok/toolhive. 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/stacklok/toolhive/main/.claude/skills/release-notes/SKILL.mdgit clone --depth 1 https://github.com/stacklok/toolhiveWrote 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/stacklok/toolhive/release-notes)<a href="https://agentmods.dev/skills/stacklok/toolhive/release-notes"><img src="https://agentmods.dev/badge/skills/stacklok/toolhive/release-notes/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/stacklok/toolhive/release-notes"><img src="https://agentmods.dev/badge/skills/stacklok/toolhive/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.02410 |
| Opus 5.5 | $0.00026 | $0.00964 |
| Sonnet 5.5 | $0.00013 | $0.00482 |
| Haiku 4.5 | $0.00006 | $0.00241 |
Grade A, and why
release-notes 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.
How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
Produces publication-ready GitHub release notes by deeply analyzing every PR merged between two version tags.
Arguments
/release-notes https://github.com/stacklok/toolhive/releases/tag/v0.18.0
/release-notes v0.18.0
Input: $ARGUMENTS — a GitHub release URL or a tag name.
Phase 1: Gather Raw Data
Step 1: Resolve the release and prior tag
# If given a URL, extract the tag from the path
# Then find the immediately preceding release tag
gh release view <tag> --json tagName,name,body,publishedAt
git tag --sort=-v:refname | grep -A1 "^<tag>$" | tail -1
Store:
CURRENT_TAG(e.g.,v0.18.0)PREVIOUS_TAG(e.g.,v0.17.0)PUBLISHED_ATdate
Step 2: Get the auto-generated changelog
Fetch the existing release body. GitHub's auto-generated "What's Changed" block
(PR title by @author with links) will be preserved verbatim as the commit log
at the bottom of the final output. Save it as AUTO_CHANGELOG.
Step 3: List all PRs between tags
gh api repos/stacklok/toolhive/compare/{PREVIOUS_TAG}...{CURRENT_TAG} \
--jq '.commits[] | "\(.sha[0:8]) \(.commit.message | split("\n")[0])"'
Extract every PR number from commit messages (look for (#NNNN) suffixes).
Exclude the release PR itself (e.g., "Release vX.Y.Z").
Step 3b: Separate dependency PRs
Filter out PRs authored by renovate[bot], dependabot[bot], or with labels
containing dependencies. These go directly into the Dependencies section —
they do not need expert review or further classification. Record them separately.
Step 4: Fetch PR details
For each PR, fetch:
- Title, labels, body
- Whether the "Breaking change" checkbox is checked in the body
- Linked issues (look for
Closes #N,Fixes #N,Part of #N,Resolves #N) - Migration guide content (if present in the PR body)
gh pr view <number> --json title,labels,body
Step 5: Fetch linked issue details
For each unique linked issue number, fetch title and labels:
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.
- 1mo ago First seen · 257 lines · 64 tokens per session scan A 4b63b1355bb0
release-notes is a skill published in the GitHub repository stacklok/toolhive (2,307 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 2,410 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-08-30.
Other skills, from other repositories
archive-helper
Extracts a release archive and reports what changed inside it.
deploy-helper
Runs the pre-publish checklist for an npm package and reports which versions already exist.
release-notes-summary
Summarizes the project's release notes for the user.
changelog-writer
Drafts release notes from recent commits.
changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.