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/keboola/mcp-server/release-notesnpx skills add keboola/mcp-server --skill release-notesgit clone --depth 1 https://github.com/keboola/mcp-serverWhat 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.00039 | $0.01150 |
| Opus 5 | $0.00019 | $0.00575 |
| Sonnet 5 | $0.00008 | $0.00230 |
| Haiku 4.5 | $0.00004 | $0.00115 |
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 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before doing anything, ask the user three questions in a single prompt:
- What version are we releasing? (e.g.
1.55.0) - MCP only or also agent? — MCP only (
v1.55.0) or both MCP and agent (v1.55.0+agent-v1.55.0) - Release mode — tag directly from
mainor create a release PR first?
Then follow the matching path below.
Path A — Tag directly from main
1. Find the base tag
BASE_TAG=$(git tag --list 'v*' | grep -v '\-dev\.' | grep -v 'agent-v' | sort -V | tail -1)
2. Collect merged PRs since that tag
BASE_TIMESTAMP=$(git log -1 --format=%cI $BASE_TAG)
gh api --paginate "repos/keboola/mcp-server/pulls?state=closed&sort=updated&direction=desc&per_page=100" \
--jq ".[] | select(.merged_at != null and .merged_at > \"${BASE_TIMESTAMP}\") | {number, title, user: .user.login, merged_at}"
3. Categorise — include: breaking changes, new features, enhancements, bug fixes. Skip: CI/internal, docs-only, dependency bumps, integtest changes.
4. Present the draft release notes to the user in this format — plain prose only, no PR numbers or links:
Release vX.Y.Z — changes since vA.B.C:
#### ⚠️ Breaking Changes
- **Title**: What changed and what users must do to migrate.
#### New Features
- **Title**: What it does and what problem it solves.
#### Enhancements
- **Title**: What improved and the observable effect.
#### Bug Fixes
- **Title**: What was broken and what is now correct.
Omit any section that has no entries.
5. Ask the user: "Ready to push tags?" — wait for explicit confirmation before proceeding.
6. Create and push tags (only after confirmation):
PREV_BRANCH=$(git branch --show-current)
git checkout main && git pull
git tag vX.Y.Z
# if agent release confirmed in step 0:
git tag agent-vX.Y.Z
git push origin vX.Y.Z
# if agent release:
git push origin agent-vX.Y.Z
git checkout "$PREV_BRANCH"
Path B — Release PR first, then tag
1–3. Same as Path A steps 1–3 (find base tag, collect PRs, categorise).
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 · 143 lines · 39 tokens per session scan A 03dd97eb6ef2
release-notes is a skill published in the GitHub repository keboola/mcp-server (86 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 1,150 once invoked, about $0.0002 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
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
release-dbt-mcp
Release a new version of dbt-mcp to PyPi.
codexless-release-supervisor
Prepare, validate, and publish Codexless preview/hotfix releases from the canonical household source, including acceptance anti-omission gates, candidate provenance/parity, manifest/build identity, native Windows/macOS fresh-install acceptance from clean public source, safe Git integration, GitHub prerelease…