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/toolhive-releasenpx skills add stacklok/toolhive --skill toolhive-releasegit 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.00077 | $0.01229 |
| Opus 5 | $0.00039 | $0.00615 |
| Sonnet 5 | $0.00015 | $0.00246 |
| Haiku 4.5 | $0.00008 | $0.00123 |
Grade A, and why
toolhive-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 2d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ToolHive Release
Automates the ToolHive release process by analyzing changes and triggering the release PR workflow.
When to Use
- When cutting a new ToolHive release
- When checking what's changed since the last release
- When deciding between patch, minor, or major version bump
- When the user says "release", "cut a release", "new version", or "version bump"
Instructions
Step 1: Find the Last Release
git tag --sort=-v:refname | head -1
This returns the most recent version tag (e.g., v0.8.3).
Step 2: List Commits Since Last Release
git log <last-tag>..HEAD --oneline --no-merges
Count the commits:
git log <last-tag>..HEAD --oneline --no-merges | wc -l
Step 3: Categorize Changes
Analyze each commit and categorize into:
| Category | Description | Version Impact |
|---|---|---|
| New Features | New functionality, new commands, new APIs | Minor bump |
| Bug Fixes | Fixes to existing functionality | Patch bump |
| Breaking Changes | API changes, removed features, incompatible changes | Major bump |
| Improvements | Enhancements to existing features, refactoring | Patch or Minor |
| Tests/CI | Test additions, CI/CD changes | No impact |
| Documentation | Doc updates, README changes | No impact |
| Dependencies | Dependency updates (Renovate PRs) | Patch bump |
Step 4: Recommend Version Bump
Based on the categorization:
- Major (
X.0.0): Any breaking changes present - Minor (
0.X.0): New features without breaking changes - Patch (
0.0.X): Only bug fixes, dependency updates, improvements
Present the recommendation with justification to the user.
Step 5: Trigger the Release Workflow
IMPORTANT: Present the analysis and recommendation to the user and WAIT for explicit confirmation before proceeding.
After user confirms the bump type, use the GitHub MCP tool to trigger the workflow:
mcp__github__run_workflow(
owner: "stacklok",
repo: "toolhive",
workflow_id: "create-release-pr.yml",
ref: "main",
inputs: { "bump_type": "<patch|minor|major>" }
)
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.
- 2d ago First seen · 155 lines · 77 tokens per session scan A e885b5b06c36
toolhive-release is a skill published in the GitHub repository stacklok/toolhive (2,065 stars, last pushed today), licensed Apache-2.0. It adds 77 tokens to every session and 1,229 once invoked, about $0.0004 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
testing-mcp-server-security
Testing Model Context Protocol (MCP) servers and the clients that consume them for tool poisoning, prompt injection via tool descriptions/outputs, over-permissioned and local-credential-stealing tools, config/trust bypasses, and unauthenticated RCE during authorized penetration tests of AI agent infrastructure.
mcp-redteam
Security audit of MCP servers. Safe mode (default) = source analysis + read-only probing. Active mode = controlled payload testing.
brin-check
Scan packages, repositories, MCP servers, domains, web pages, and agent skills for security threats using the brin API. Use this skill before installing dependencies, visiting URLs, or integrating external resources.
browser-control
Requires BROWSERAPIKEY in .env.
browser-skill
Imported from OpenClaw migration.
bugcrowd-reporting
Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints…