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 Abilityai/abilities --skill releasegit clone --depth 1 https://github.com/Abilityai/abilitiesWrote 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/abilityai/abilities/release)<a href="https://agentmods.dev/skills/abilityai/abilities/release"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/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/abilityai/abilities/release"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/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.00041 | $0.01131 |
| Opus 5.5 | $0.00016 | $0.00452 |
| Sonnet 5.5 | $0.00008 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
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 1mo 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.release vX.Y — recent: <summary>. Then proceed.
Automate the release cut process: pre-release checklist, version bump, release notes, PR creation, and tagging.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| GitHub Issues | GitHub repo | ✅ | ✅ | In-dev issues to close |
| Git log | current branch | ✅ | Commits since last release | |
| Version file | pyproject.toml, package.json, etc. |
✅ | ✅ | Version bump |
| Changelog | docs/memory/changelog.md |
✅ | ✅ | Release notes |
Arguments
$ARGUMENTS: Version tag (e.g.,v1.2.0,cli-v0.4.0). If omitted, suggests next version based on git tags.
Process
Step 1: Determine Version
If no version argument provided:
# Get latest tag
git describe --tags --abbrev=0 2>/dev/null || echo "No tags yet"
Suggest next version following semver. Confirm with user before continuing.
Step 2: Pre-Release Checklist
Run validation gates. Do NOT proceed if any CRITICAL item fails.
# 1. No open P0 issues
gh issue list --label "priority-p0" --state open --json number,title
# 2. No open P1 issues that are blocking
gh issue list --label "priority-p1,status-blocked" --state open --json number,title
# 3. Tests pass
# (invoke test-runner or check CI status)
gh run list --limit 5 --json status,conclusion,name
Present checklist:
## Pre-Release Checklist
- [ ] No open P0 issues
- [ ] No blocked P1 issues
- [ ] Tests passing (CI green)
- [ ] In-dev issues confirmed shippable
GATE: Ask user to confirm checklist before continuing.
Step 3: Collect In-Dev Issues
gh issue list --label "status-in-dev" --state open --json number,title
These issues will be closed by the release PR via Closes #N.
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.
- 1mo ago First seen · 165 lines · 41 tokens per session scan A ec71ebf54ac0
release is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 1,131 once invoked, about $0.0002 per session on Opus 5.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-07.
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.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
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.