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 agentmods add skills/stacklok/toolhive/release-notesnpx skills add stacklok/toolhive --skill release-notesgit clone --depth 1 https://github.com/stacklok/toolhiveWhat 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 | $0.00064 | $0.02410 |
| Opus 5 | $0.00032 | $0.01205 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 257 lines · 64 tokens per session scan A 4b63b1355bb0
release-notes is a skill published in the GitHub repository stacklok/toolhive (2,056 stars, last pushed yesterday), licensed Apache-2.0. It adds 64 tokens to every session and 2,410 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-30.
Other skills, from other repositories
network-rca
Kubernetes network root cause analysis skill powered by Kubeshark MCP. Use this skill whenever the user wants to investigate past incidents, perform retrospective traffic analysis, take or manage traffic snapshots, extract PCAPs, dissect L7 API calls from historical captures, compare traffic patterns over time, detect…
kfl
KFL2 (Kubeshark Filter Language) reference. This skill MUST be loaded before writing, constructing, or suggesting any KFL filter expression. KFL is statically typed — incorrect field names or syntax will fail silently or error. Do not guess at KFL syntax without this skill loaded. Trigger on any mention of KFL, CEL…
security-audit
Kubernetes network security audit skill powered by Kubeshark MCP. Use this skill whenever the user wants to audit a cluster for security threats, detect compromised workloads, find malicious traffic patterns, hunt for indicators of compromise (IOCs), check for data exfiltration, identify C2 (command and control)…
install
Kubeshark installation and deployment skill. Use this skill whenever the user wants to install Kubeshark, deploy Kubeshark to a Kubernetes cluster, set up Kubeshark, configure Kubeshark helm values, generate a Kubeshark config file, customize Kubeshark deployment, troubleshoot Kubeshark installation, upgrade…
qa-find-bugs
Drive the live product at https://dashboard.bex.co as a signed-in QA user (QAEMAIL / QAPASSWORD from .env), hunt real bugs across the hosting features, research each fix down to file:line, file the non-duplicate findings to the w6 board through /pm, and /ship the scheduled milestone. Use when the user asks to QA the…
pm
Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as creating, promoting, adding, or completing work.