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 mhmdreza-rafiei/agent-tools --skill releasegit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/release)<a href="https://agentmods.dev/skills/mhmdreza-rafiei/agent-tools/release"><img src="https://agentmods.dev/badge/skills/mhmdreza-rafiei/agent-tools/release/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/mhmdreza-rafiei/agent-tools/release"><img src="https://agentmods.dev/badge/skills/mhmdreza-rafiei/agent-tools/release.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.00068 | $0.00701 |
| Opus 5 | $0.00034 | $0.00351 |
| Sonnet 5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
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 8d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release
Cut a release as one consistent operation: changelog → version bump → tag → notes. A release done by hand drifts (forgotten changelog, wrong bump, missing tag); this skill makes the four steps agree.
When to use
When the user says "cut a release", "ship a version", "generate the
changelog"; on /release; before announcing a version.
Commands
/release <major|minor|patch>— bump per semver and cut./release <version>— cut a specific version (e.g./release 2.0.0)./release --dry-run— print the changelog + tag without writing.
Step 1 — Detect the version scheme
- Read the manifest (
package.json,pyproject.toml,Cargo.toml,VERSION, git tags) to find the current version and the scheme (semver, calver, custom). - If no scheme is detectable, ask once which to use.
Step 2 — Generate the changelog
- Collect commits since the last tag using Conventional Commits:
feat→ Features,fix→ Fixes,perf→ Performance,docs→ Docs,refactor/chore→ Maintenance (collapse if noisy). - Group by type; one line per commit, scope in parens.
- Append an "Unreleased" → "" heading.
Step 3 — Bump + tag
- Bump per the requested type or explicit version.
- Update the manifest(s) in one commit:
chore(release): vX.Y.Z. - Tag
vX.Y.Zon that commit. Do not push unless the user asks.
Step 4 — Release notes
- A short summary (1–3 lines) of what this release is about.
- The grouped changelog from step 2.
- Breaking changes (if any) called out at the top.
Output
CHANGELOG.mdupdated (or created).- Manifest version bumped.
- Tag
vX.Y.Zcreated (not pushed). - Release notes printed to chat.
Constraints
- Follow
rule/global/git-workflow: never push without explicit user ask; never rewrite history without permission. - Conventional Commits only; if the repo has non-conforming commits, list them and ask before guessing their type.
- Do not include secrets or uncommitted files in the release commit.
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.
- 8d ago First seen · 75 lines · 68 tokens per session scan A 2987f38e2190
release is a skill published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 24d ago), licensed MIT. It adds 68 tokens to every session and 701 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-09-03.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.