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/anthonyposchen/agent-skills/releasenpx skills add AnthonyPoschen/agent-skills --skill releasegit clone --depth 1 https://github.com/AnthonyPoschen/agent-skillsWrote 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/anthonyposchen/agent-skills/release)<a href="https://agentmods.dev/skills/anthonyposchen/agent-skills/release"><img src="https://agentmods.dev/badge/skills/anthonyposchen/agent-skills/release.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 | $0.00053 | $0.01551 |
| Opus 5 | $0.00026 | $0.00776 |
| Sonnet 5 | $0.00011 | $0.00310 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
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 4d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Use this skill to maintain release records and, when asked, prepare or publish a release. Write release notes for the person deciding whether to upgrade, install, review, or publish.
Activation
Use this skill for:
- changelogs
- release notes
- GitHub release text
- changes since a tag
- changes between versions
- upgrade notes
- release summaries
- release PR descriptions
- release versions, tags, and publishing
- missing, stale, or incorrect changelog and release-note records
Choose The Release Task
- Release records: create, update, review, or correct a changelog, release note, GitHub Release draft, or release summary. Do not tag or publish unless the user asks.
- Prepare a release: determine the version, make required release-record updates, and report the commit that is ready to tag. Do not create or push a tag unless the user asks.
- Publish a release: complete the release records, create the requested tag, and publish it only with explicit authority.
Convention Detection
Before writing files, inspect existing conventions:
CHANGELOG.mdCHANGELOG*docs/releases/docs/changelog/releases/.github/releases/- previous GitHub release text when available
Follow the existing convention unless the user asks to change it. If no convention exists, prefer producing release notes text instead of creating files automatically. Ask before introducing a new changelog storage convention.
Also inspect existing tags, package manifests, release automation, and release documentation. They establish the repository's versioning convention.
Choose A Version
Follow the repository's established versioning scheme. Existing tags, package metadata, release documents, and automation take priority over this skill.
- For a repository that uses Semantic Versioning, follow its normal major/minor/patch practice. Ask before choosing a version when the compatibility impact is unclear.
- When no clear versioning convention exists, use CalVer. Read CalVer details before choosing or creating a CalVer tag.
- Do not change a repository from one versioning scheme to another as part of a normal release. Ask first.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 213 lines · 53 tokens per session scan A 3c116d58186e
release is a skill published in the GitHub repository AnthonyPoschen/agent-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 1,551 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-31.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…