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/implement-story/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/implement-story)<a href="https://agentmods.dev/skills/stacklok/toolhive/implement-story"><img src="https://agentmods.dev/badge/skills/stacklok/toolhive/implement-story/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/implement-story"><img src="https://agentmods.dev/badge/skills/stacklok/toolhive/implement-story.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.00027 | $0.02083 |
| Opus 5.5 | $0.00011 | $0.00833 |
| Sonnet 5.5 | $0.00005 | $0.00417 |
| Haiku 4.5 | $0.00003 | $0.00208 |
Grade A, and why
implement-story 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement User Story
Takes a GitHub user story issue and produces well-organized PR(s) that reliably meet the acceptance criteria.
Arguments
The user provides a GitHub issue number or URL. Example:
/implement-story #4550
/implement-story https://github.com/stacklok/toolhive/issues/4550
Phase 1: Gather Context
1.1 Read the Issue
Fetch the issue body using GitHub tools. Extract:
- User story: The "As a / I want / so that" statement
- Acceptance criteria: The checkbox list — this is the contract
- Context links: RFC links, related issues, dependencies
- Out of scope: What NOT to do
1.2 Fetch RFC Context
If the issue links to an RFC (look for THV-XXXX references or links to toolhive-rfcs):
- Clone or locate the RFC repo locally (check
../toolhive-rfcs/first) - Read the full RFC document
- Extract design decisions relevant to this story — config shapes, algorithm details, error formats, key schemas, etc.
If no RFC is linked, skip this step.
1.3 Find Related Stories
Search for sibling stories that share context with this one. These inform how to factor the code for extensibility:
# Search by keywords from the issue title
gh search issues "<keywords>" --repo stacklok/toolhive --state open --limit 10
# Search for issues linking to the same RFC
gh search issues "THV-XXXX" --repo stacklok/toolhive --limit 10
For each related story, read its acceptance criteria. Ask:
- Will a future story need to extend a type, interface, or package I'm creating?
- Should I define an interface now that a sibling story will implement later?
- Are there naming conventions or patterns I should establish that siblings will follow?
Do not implement sibling stories. Design internal interfaces so they can be extended without refactoring, but do not add config fields, CRD types, or user-facing API surface for functionality that isn't implemented in this PR. Unused config confuses users and reviewers.
1.4 Research the Codebase
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 · 235 lines · 27 tokens per session scan A 043ceec2634a
implement-story is a skill published in the GitHub repository stacklok/toolhive (2,307 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 2,083 once invoked, about $0.0001 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
changelog-writer
Write a CHANGELOG entry from the commits since the last tag, grouped into added, changed and fixed.
git-commit-message
Write a commit message from the staged diff: a short summary line and a body explaining why.
git-commit
Commit to Git safely: runs tests, security-reviews the diff, strips secrets and dead code, and enforces clean messages. Use before any commit or push.
summarize-changes
Summarizes uncommitted changes and flags anything risky.
changelog
Generates a changelog entry from recent commits.
git-pushing-hardened
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.