Borrowing it
Nothing to install: this file belongs to buildkite/buildkite-mcp-server. 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/buildkite/buildkite-mcp-server/main/.agents/skills/release-notes/SKILL.mdgit 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/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/buildkite/buildkite-mcp-server/release-notes"><img src="https://agentmods.dev/badge/skills/buildkite/buildkite-mcp-server/release-notes.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.00047 | $0.00692 |
| Opus 5.5 | $0.00019 | $0.00277 |
| Sonnet 5.5 | $0.00009 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
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 15d 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 — 69 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.27.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, kept brief. For each new tool, give its name, toolset, a one-line purpose, and its required scope, destructive status, and read-only mode availability. Describe changes to existing tools in more detail when callers could see different results, such as a changed default. Leave out arguments, response fields, states, and validation rules that the tool description already gives agents.## 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.
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.
- 15d ago Changed · +4 lines 466803a01af4
- 1mo ago 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 (56 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 692 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
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-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.
repository-manager-workspace-release
Preview the topologically-phased version-bump plan across a workspace, drive validation with an explicitly consented chain into version bump and phased push, and manage the workspace.yml manifest — via rmworkspace and rmprojects. Nothing here pushes or bumps without an explicit opt-in on the call that triggers it…
repository-manager-bulk-git-operations
Bulk, parallel git operations across a whole workspace of repositories via the repository-manager MCP server — clone, pull, push, add, commit, pre-commit, phased push, and enumerate every repo across a GitLab instance / GitHub org into an ingest manifest (which also natively ingests them into the knowledge graph as…