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 ai-driven-dev/framework --skill 03-release-taggit clone --depth 1 https://github.com/ai-driven-dev/frameworkWrote 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/ai-driven-dev/framework/03-release-tag)<a href="https://agentmods.dev/skills/ai-driven-dev/framework/03-release-tag"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/03-release-tag/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/ai-driven-dev/framework/03-release-tag"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/03-release-tag.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.00298 |
| Opus 5.5 | $0.00022 | $0.00119 |
| Sonnet 5.5 | $0.00011 | $0.00060 |
| Haiku 4.5 | $0.00006 | $0.00030 |
Grade A, and why
03-release-tag 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.
What it actually says
Release Tag
Cuts annotated semver releases with notes derived from recent commits.
Actions
| # | Action | Role | Input |
|---|---|---|---|
| 01 | release-tag |
Compute version, draft notes, validate, bump, tag, push | version (optional), notes_overrides |
Before running an action, read its file in actions/, not only the table or assets.
Transversal rules
- Versions follow semver
major.minor.patchstrictly. No suffixes unless explicitly requested. - Tags are annotated (
git tag -a), never lightweight. - Release notes are mandatory and follow
assets/release-template.md. - Always ask the user to validate the version, notes, and impacted files before tagging.
- Never
--forcepush tags. Use--force-with-leaseonly when explicitly required. - The bump commit only includes version-manager files (e.g.
package.json,pyproject.toml).
Assets
assets/release-template.md: Release notes template.
What ships with it
2 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.
- 1mo ago Changed · -9 lines · -61 tokens per session a8aac3003c65
- 1mo ago First seen · 40 lines · 116 tokens per session scan A 8f95bd82f55c
03-release-tag is a skill published in the GitHub repository ai-driven-dev/framework (522 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 298 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-08-30.
Other skills, from other repositories
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
ship-change
Ship an OpenSpec change after openspec-apply completes. When only QA/manual tasks remain, marks them done (tested later), archives + syncs specs, commits, pushes, opens a PR against develop, watches CI, waits for CodeRabbit, auto-applies safe fixes and re-pushes, loops until CI green + no actionable review threads…
release-bump-changelog
Use this skill when preparing a release bump or updating release notes. It writes a launch-style release story from the actual change set, then runs cargo bump so the generated GitHub notes and the marketing copy land together in CHANGELOG.md.
akiship
Full release ritual end-to-end — front-loaded checks, then an unattended pass. ACTIVATION = the literal token /akiship, or an imperative turn, in any language, ordering the release ritual for this repo. A question about it, or a completion word with no release object, activates nothing — consult the checklist and…
project-release-check
Validate this example project's release readiness. Use before publishing a release candidate.