Borrowing it
Nothing to install: this file belongs to membrane/api-gateway. 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/membrane/api-gateway/master/.claude/skills/release-notes/SKILL.mdgit clone --depth 1 https://github.com/membrane/api-gatewayWrote 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/membrane/api-gateway/release-notes)<a href="https://agentmods.dev/skills/membrane/api-gateway/release-notes"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/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/membrane/api-gateway/release-notes"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/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.00124 | $0.01639 |
| Opus 5.5 | $0.00050 | $0.00656 |
| Sonnet 5.5 | $0.00025 | $0.00328 |
| Haiku 4.5 | $0.00012 | $0.00164 |
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 2mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release notes
Produce release notes for the next Membrane release by diffing master against the last release and turning the intervening commits into a clean, grouped, PR-linked changelog — the kind that goes on the project's GitHub Releases page.
Repo: membrane/api-gateway. PR URL pattern: https://github.com/membrane/api-gateway/pull/<N>.
1. Determine the range: <base>..master
The base is the last released version. Releases are marked by a commit whose subject is
Release X.Y.Z (#PR) (immediately followed by a Snapshot version commit). The local tags
lag behind, so detect the base from these commits, not from git tag.
- If the user named a version (e.g. "since 7.2.3"), use that commit as the base:
# Note the trailing space — git uses POSIX regex, so `\b` is NOT supported here. BASE=$(git log -E --grep="^Release 7\.2\.3 " --format=%H master | head -1) - Otherwise auto-detect the most recent release:
Take its hash asgit log -E --grep="^Release [0-9]+\.[0-9]+\.[0-9]+ " --format="%H %s" master | head -1BASEand read the version from its subject.
The new version being released is the pom version minus -SNAPSHOT:
grep -m1 '<version>' pom.xml # e.g. 7.2.4-SNAPSHOT -> 7.2.4
Sanity-check the range before writing anything:
git log --oneline $BASE..master | wc -l # how many commits
git log --pretty="%s" $BASE..master # the subjects to triage
If the range is empty (master == last release), say so and stop.
2. Collect and enrich
For each commit on $BASE..master, pull the subject and the trailing PR number:
git log --pretty="%s" $BASE..master
Most subjects end in (#NNNN) — that's the PR. Turn it into a link
[#NNNN](https://github.com/membrane/api-gateway/pull/NNNN). If a subject has two trailing
numbers (e.g. ... (#2988) (#2995)), the last one is the merge PR — link that one.
Read the subject for meaning; rewrite terse or type:-prefixed subjects into a user-facing
sentence. Strip conventional-commit prefixes (feat:, fix:, chore:, build:, refactor:,
docs:) from the displayed text — they only inform which group the entry belongs in.
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.
- 2mo ago First seen · 121 lines · 124 tokens per session scan A 0322b80b9e27
release-notes is a skill published in the GitHub repository membrane/api-gateway (656 stars, last pushed yesterday), licensed Apache-2.0. It adds 124 tokens to every session and 1,639 once invoked, about $0.0005 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
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
github-cli
A command-line tool connection for GitHub tasks that built-in tools do not cover. It uses GitHub's command-line program to work with issues, pull requests, releases, workflows, searches, and the GitHub API.
fastapi-expert
Expert-level FastAPI development for high-performance Python APIs with async support. Use when the user mentions Python, API, async, REST, OpenAPI, or Pydantic, or when the task involves FastAPI Features.
openapi-expert
Expert-level OpenAPI/Swagger specification for API design, documentation, and code generation. Use when the user mentions swagger, API specs, REST, API design, or documentation, or when the task involves OpenAPI Specification, Webhooks, or Polymorphism.
construtor-de-api
Construção e documentação de APIs REST e GraphQL: design de endpoints, versionamento, autenticação, tratamento de erros, documentação OpenAPI 3.0 e boas práticas de segurança e performance.