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/buildkite/buildkite-mcp-server/release-notesnpx skills add buildkite/buildkite-mcp-server --skill release-notesgit clone --depth 1 https://github.com/buildkite/buildkite-mcp-serverWrote 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/buildkite/buildkite-mcp-server/release-notes)<a href="https://agentmods.dev/skills/buildkite/buildkite-mcp-server/release-notes"><img src="https://agentmods.dev/badge/skills/buildkite/buildkite-mcp-server/release-notes.svg" alt="Measured on agentmods" 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.00047 | $0.00622 |
| Opus 5 | $0.00023 | $0.00311 |
| Sonnet 5 | $0.00009 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release notes
Produce accurate, maintainer-reviewed GitHub release notes that follow the style of recent curated releases in this repository.
Gather evidence
- Confirm the target version and inspect its current GitHub release, if one exists.
- Identify the comparison base from the release series and verify the full comparison range. Do not rely only on locally fetched tags.
- Inspect a recent curated release, such as
v1.19.0, for layout and level of detail. Treat it as a style reference, not a fixed template. - Collect every pull request in the comparison range. Read the pull request descriptions and changed files for user-facing changes. Inspect source at the target tag when needed to verify tool names, arguments, defaults, limits, and behavior.
Use gh for GitHub data when available. Do not infer technical details from pull
request titles alone.
Draft the release
Start with a short paragraph describing the most important user outcomes. Then use the following sections when they have relevant content:
## What's Changed, with concise categories such as Features, Agent Guidance, Development and Evals, and Dependencies.## Tool Changes, describing new tools and material changes to existing tools in practical terms.## New Contributors, when applicable.- A
**Full Changelog**comparison link as the final line.
For each pull request in What's Changed, preserve its title, author attribution,
and URL. Ensure every pull request in the comparison range appears exactly once
in those categorized lists. The narrative Tool Changes section may discuss the
same work without repeating attribution.
Prefer concise, factual language. Focus on externally observable behavior and agent outcomes. Exclude implementation detail unless it explains a limit, compatibility constraint, or operational risk. Do not use em dashes.
Review and update
Always show the complete Markdown draft and stop. Wait for a new user response that explicitly approves that exact body before changing GitHub, even when the initial request asks to draft and update the release in one step. Approval to draft notes or general permission to update a release is not approval of the generated body. If the draft changes, present the complete revised Markdown and wait for approval again. After approval:
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 · 65 lines · 47 tokens per session scan A 5d11c2cb8d84
release-notes is a skill published in the GitHub repository buildkite/buildkite-mcp-server (53 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 622 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-09-05.
Other skills, from other repositories
changelog-writer
Write changelogs for Bifrost releases. Reads git history, bumps module versions following the core→framework→plugins→transport hierarchy, writes transports/changelog.md (enterprise-style) and per-module changelog.md files, and updates version files. Invoked with /changelog-writer or /changelog-writer .
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…
release-checklist
Pre-release safety audit for the Bifrost repo. Scans database migrations changed in a release for high-scale deadlock / lock-contention risks and for work that blocks application boot time, then produces a pass/warn/fail report with a concrete remediation plan. Invoked with /release-checklist [git-ref-range]. Built to…
xcodebuildmcp-docs-release-review
Use when reviewing XcodeBuildMCP documentation, CLI command references, website manifest generation, changelog, release notes, and release script changes.
portainer-mcp-release
How to cut a portainer-mcp release that bumps the embedded Portainer OpenAPI spec to a new Portainer minor (e.g. 2.41.x → 2.42.x). Walks through finding the upstream patch target, regenerating the spec, recounting ops/tags per profile, refreshing the orphan-tag inventory, bumping version pins across the README and…
prepare-release
Prepare a new touchdesigner-mcp release: inspect the unreleased diff since the last tag, decide independently how the MCP package version and the MCP API version each move (the API axis stays put unless the server/API contract changed), write the CHANGELOG entry, bump the six version-bearing files, commit, and open…