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 skills add d0hx4n2503/Agent-Skills --skill release-notegit clone --depth 1 https://github.com/d0hx4n2503/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/d0hx4n2503/agent-skills/release-note)<a href="https://agentmods.dev/skills/d0hx4n2503/agent-skills/release-note"><img src="https://agentmods.dev/badge/skills/d0hx4n2503/agent-skills/release-note/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/d0hx4n2503/agent-skills/release-note"><img src="https://agentmods.dev/badge/skills/d0hx4n2503/agent-skills/release-note.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.01665 |
| Opus 5 | $0.00005 | $0.00833 |
| Sonnet 5 | $0.00002 | $0.00333 |
| Haiku 4.5 | $0.00001 | $0.00167 |
Grade A, and why
release-note 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 9d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Versioning (SemVer) Release Notes Guideline
This document defines the standard steps and rules for writing Release Notes for the project, based on Semantic Versioning 2.0.0 (semver.org).
1. Core Rules of SemVer (X.Y.Z)
Every release version must follow the MAJOR.MINOR.PATCH format (e.g., 1.4.2). You must increment the respective element based on the scope of changes:
- MAJOR (X): Increment when you make incompatible API changes (Breaking changes). When MAJOR is incremented, MINOR and PATCH must be reset to
0(e.g.,1.4.2$\rightarrow$2.0.0). - MINOR (Y): Increment when you add functionality in a backward-compatible manner. When MINOR is incremented, PATCH must be reset to
0(e.g.,1.4.2$\rightarrow$1.5.0). - PATCH (Z): Increment when you make backward-compatible bug fixes without adding new features or breaking existing APIs (e.g.,
1.4.2$\rightarrow$1.4.3).
Note: Major version zero (
0.x.x) is for initial development. Anything MAY change at any time. The public API should not be considered stable.
1.1. Additional Labels (Pre-release & Build Metadata)
SemVer allows appending labels to define the lifecycle of a release more precisely:
- Pre-release: Denoted by a hyphen
-immediately following the PATCH version. These versions have a lower precedence than the associated normal version and are used for drafts or testing phases.- Examples:
1.0.0-alpha,1.0.0-beta.1,1.0.0-rc.1(Release Candidate). - Precedence:
1.0.0-alpha<1.0.0-beta<1.0.0-rc.1<1.0.0.
- Examples:
- Build Metadata: Denoted by a plus sign
+at the very end. Used to store commit hashes, build IDs, or timestamps. This metadata does not affect version precedence.- Examples:
1.0.0-beta.1+exp.sha.5114f85,1.2.3+20260601.
- Examples:
2. Step-by-Step: Writing Release Notes
When preparing a new release, follow these steps:
Step 1: Categorization
List all merged tickets/PRs. Group them into clear categories (following Keep a Changelog standards):
Added: For new features.Changed: For changes in existing functionality.Deprecated: For once-stable features removed in upcoming releases.Removed: For deprecated features removed in this release.Fixed: For any bug fixes.Security: To invite users to upgrade in case of vulnerabilities.
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.
- 9d ago First seen · 116 lines · 9 tokens per session scan A 1d91a4095462
release-note is a skill published in the GitHub repository d0hx4n2503/Agent-Skills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 1,665 once invoked, about $0.0000 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
project-release-maintainer
Project overlay for release and packaging maintenance across install layout, shipped assets, automation, license and notice alignment, and release docs. Not for content-only documentation or publishing without explicit authorization.
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
changelog
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.
git-workflow
A Git workflow guide for organizing commits, branches, pull requests, releases, and automated version-control tasks. Git is the system developers use to track code changes and collaborate.
git-publish-release
A release assistant for GitHub, a service for hosting software projects. It compares project history and creates a GitHub Release with notes for a chosen version tag.
log-changes
Use when asked to update the changelog, document version changes, prepare a release, or add entries for recent work, and when reviewing a diff or pull request that touches CHANGELOG.md. Produces concise user-facing CHANGELOG.md entries, follows Keep a Changelog and Semantic Versioning, and verifies that new bullets…