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 paulo-yamagishi/claude-code-setup --skill releasegit clone --depth 1 https://github.com/paulo-yamagishi/claude-code-setupWrote 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/paulo-yamagishi/claude-code-setup/release)<a href="https://agentmods.dev/skills/paulo-yamagishi/claude-code-setup/release"><img src="https://agentmods.dev/badge/skills/paulo-yamagishi/claude-code-setup/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.1 | $0.00000 | $0.00383 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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.
What it actually says
/release — Bump Version and Tag a Release
Automates semantic version bumps, changelog updates, and git tagging.
Usage
/release <major|minor|patch>
Steps
- Read current version from
VERSIONfile at repo root - Bump version according to the argument:
major: X.0.0 (breaking changes)minor: X.Y+1.0 (new features)patch: X.Y.Z+1 (fixes)
- Update
CHANGELOG.md:- Rename
## [Unreleased]section to## [NEW_VERSION] - YYYY-MM-DD - Add a fresh empty
## [Unreleased]section above it - Update comparison links at the bottom of the file
- Rename
- Update
VERSIONfile with the new version string - Commit all changes with message:
chore: release vNEW_VERSION - Create git tag
vNEW_VERSIONon the new commit
Rules
- Abort if the
## [Unreleased]section in CHANGELOG.md is empty (nothing to release) - Abort if working tree is dirty (uncommitted changes besides the release edits)
- Always verify the final state:
cat VERSION && git tag -l 'vNEW_VERSION' - Do NOT push — let the user decide when to push
Example
/release patch
# VERSION: 0.1.0 → 0.1.1
# CHANGELOG: [Unreleased] → [0.1.1] - 2026-02-09
# Commit: chore: release v0.1.1
# Tag: v0.1.1
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 · 42 lines · 0 tokens per session scan A ce6fb664511f
release is a skill published in the GitHub repository paulo-yamagishi/claude-code-setup (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 383 tokens. 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
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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.