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 skills add steph-dove/klaussy-agents --skill fastapi-releasegit clone --depth 1 https://github.com/steph-dove/klaussy-agentsWrote 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/steph-dove/klaussy-agents/fastapi-release)<a href="https://agentmods.dev/skills/steph-dove/klaussy-agents/fastapi-release"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/fastapi-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/steph-dove/klaussy-agents/fastapi-release"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/fastapi-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.00064 | $0.02119 |
| Opus 5 | $0.00032 | $0.01059 |
| Sonnet 5 | $0.00013 | $0.00424 |
| Haiku 4.5 | $0.00006 | $0.00212 |
Grade A, and why
fastapi-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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- httpx-release — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a release: pick the next version, update every place the version is declared, write the changelog from the conventional commits since the last release, and tag. Stop before pushing or publishing unless the user asked for those too.
Phase 1: Establish the baseline
- Find the current version and every file that declares it. Read CLAUDE.md for the version location, then confirm by searching — a project often repeats the version in more than one file (e.g.
pyproject.tomlandsrc/<pkg>/__init__.py, orpackage.jsonand a lockfile). List them all; a release that bumps one and misses another ships an inconsistent version. - Find the last release tag.
git describe --tags --abbrev=0(fall back to the first commit if there are no tags). This is the range boundary for the changelog. - Collect the commits since that tag.
git log <last-tag>..HEAD --oneline. If there are none, there's nothing to release — say so and stop.
Phase 2: Choose the next version
Derive the bump from the conventional-commit types in the range (semver):
- major — any commit with a
!(e.g.feat!:) or aBREAKING CHANGE:footer. - minor — at least one
feat:and no breaking change. - patch — only
fix:/perf:/refactor:/docs:/chore:etc.
State the computed version and the reason before changing anything. If the user named a specific version, use theirs; if the commits disagree with it (e.g. they said patch but there's a feat!), flag the mismatch and let them decide.
Phase 3: Apply the bump
- Update the version in every file found in Phase 1 — edit the literal, don't reformat the file.
- Update the changelog. If a
CHANGELOG.mdexists, follow its existing format exactly; otherwise create one in the Keep a Changelog style. Add a new section for this version dated with the real date (rundate +%F— do not guess it). Group entries by type (Added / Fixed / Changed / Removed) from the commit subjects; write them for a human reader, not as raw commit lines. - Do not touch anything unrelated to the release.
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.
- 10d ago First seen · 78 lines · 64 tokens per session scan A 6a0851f26d32
fastapi-release is a skill published in the GitHub repository steph-dove/klaussy-agents (16 stars, last pushed 13d ago), licensed MIT. It adds 64 tokens to every session and 2,119 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
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
skillshare-release
End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASENOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version.…
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…