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 ragnarok22/agent-skills --skill create-releasegit clone --depth 1 https://github.com/ragnarok22/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/ragnarok22/agent-skills/create-release)<a href="https://agentmods.dev/skills/ragnarok22/agent-skills/create-release"><img src="https://agentmods.dev/badge/skills/ragnarok22/agent-skills/create-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.00073 | $0.02840 |
| Opus 5 | $0.00036 | $0.01420 |
| Sonnet 5 | $0.00015 | $0.00568 |
| Haiku 4.5 | $0.00007 | $0.00284 |
Grade A, and why
create-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 6d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Release
Prepare and execute a semantic version release by bumping version strings, updating changelogs, committing changes, tagging, and optionally publishing a GitHub release.
Workflow
Step 1: Detect version locations
Scan the repository root for files that contain version strings. Check these files in order:
- Node.js:
package.json(fieldversion),package-lock.json,lerna.json - Python:
pyproject.toml(fieldsproject.versionortool.poetry.version),setup.cfg(fieldversion),setup.py(argumentversion=),__version__.pyor_version.pyin source directories,version.py - Rust:
Cargo.toml(fieldversionunder[package]) - Java/Kotlin:
build.gradleorbuild.gradle.kts(propertyversion),pom.xml(element<version>under<project>) - iOS/React Native:
app.json(fieldexpo.versionorversion),Info.plist(CFBundleShortVersionString) - Generic:
version.txt,VERSION
Search commands:
# Find candidate version files
find . -maxdepth 3 \( \
-name "package.json" -o -name "pyproject.toml" -o \
-name "setup.cfg" -o -name "setup.py" -o \
-name "Cargo.toml" -o -name "build.gradle" -o \
-name "build.gradle.kts" -o -name "pom.xml" -o \
-name "app.json" -o -name "version.txt" -o \
-name "VERSION" -o -name "lerna.json" \
\) -not -path "*/node_modules/*" -not -path "*/.git/*" \
-not -path "*/vendor/*" -not -path "*/target/*"
# Find Python version files
find . -maxdepth 4 \( \
-name "__version__.py" -o -name "_version.py" -o \
-name "version.py" \
\) -not -path "*/node_modules/*" -not -path "*/.git/*" \
-not -path "*/.venv/*" -not -path "*/venv/*"
For each detected file, extract the current version string and record it. If multiple version files exist, verify they contain the same version. If versions are inconsistent, report the discrepancy to the user and ask which version to treat as canonical before proceeding.
If no version files are found, ask the user where versions should be stored and create the entry during the bump step.
What ships with it
3 files 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.
- 6d ago First seen · 291 lines · 73 tokens per session scan A 411044462e3c
create-release is a skill published in the GitHub repository ragnarok22/agent-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 2,840 once invoked, about $0.0004 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.
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.