Borrowing it
Nothing to install: this file belongs to agentdecksdk/agentdeck. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agentdecksdk/agentdeck/dev/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/agentdecksdk/agentdeckWrote 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/agentdecksdk/agentdeck/release)<a href="https://agentmods.dev/skills/agentdecksdk/agentdeck/release"><img src="https://agentmods.dev/badge/skills/agentdecksdk/agentdeck/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/agentdecksdk/agentdeck/release"><img src="https://agentmods.dev/badge/skills/agentdecksdk/agentdeck/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.00029 | $0.01068 |
| Opus 5.5 | $0.00012 | $0.00427 |
| Sonnet 5.5 | $0.00006 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release agentdeck
Follow the release process strictly. All work starts on dev; main is release-only,
and dev is the repository's default branch.
Two PRs, two issues
A release needs two labeled chore issues and two PRs, not one of each.
| PR | base | issue | closing keyword |
|---|---|---|---|
| bump | dev |
its own labeled chore issue |
Closes #N, works: dev is default |
| promotion | main |
its own labeled chore issue |
Refs #N only, close by hand: main is not default, so GitHub never creates the closing reference |
git push origin dev is rejected directly ("push declined due to repository rule violations").
The bump goes through its own PR into dev.
A PR body closing more than one issue needs one Fixes #N (or Closes #N) per line: GitHub's
closing-keyword parser only recognizes the first reference in a comma-separated list, silently
leaving the rest open (#541).
Release Steps
- Version: Confirm SemVer bump (
pyproject.tomlandCHANGELOG.md). - Preflight: Verify clean working tree, non-empty
[Unreleased]section, andmake checkis 100% green. Run it unpiped (make check, notmake check | tail) so its own exit code is what you read; a pipe reports the last command's status, not the gate's. - Bump issue:
python scripts/release_bump.py issues X.Y.Zcreates (or reuses) thevX.Y.Zmilestone, assigns it to every issue closed by a PR merged since the last tag (read from that PR'sclosingIssuesReferences; a direct push falls back to scanning its message forFixes/Closes), opens the labeledchore: cut and ship vX.Y.Zissue, and prints its number. - Bump PR into
dev:python scripts/release_bump.py bump X.Y.Zupdatespyproject.toml's version and movesCHANGELOG.md's[Unreleased]entries to a dated## [X.Y.Z]heading with compare links.- Run
python scripts/generate_docs_reference.pyonce, then verifypython scripts/generate_docs_reference.py --check. - Snapshot the docs site only if this release removes or changes a documented surface, not on
every release (
docs/delivery/docs-site-plan.mdDS-D3). A patch documenting the same surface owes nothing. - Commit:
chore(release): vX.Y.Z. Open the PR against the bump issue from step 3 (Closes #N), wait for every required check, merge.
- Promotion issue:
python scripts/release_bump.py promote X.Y.Zopens the labeledchore: release vX.Y.Z to mainissue in the same milestone and prints its number. - Promotion PR,
devtomain: Open it against the promotion issue from step 5 (Refs #N).Issue hygiene,slop, andCheck affected documentationskip themselves on amain-based PR: each already ran the real per-PR version of itself againstdevat merge time, and this diff is the whole release cycle re-evaluated, not a new change. Wait forcheckandBuild documentation, then merge and close the promotion issue by hand. - Tag:
git tag vX.Y.Z && git push origin vX.Y.Z.release.ymlpublishes to PyPI on this push; there is no undo once the tag lands. - Close the milestone:
python scripts/release_bump.py close-milestone X.Y.Z, right after the tag push. Every past release skipped this:v5.0.0throughv5.1.0all shipped with 0 open issues but stayed open on GitHub. - Deploy: In the
prod/worktree (detached on a tag on purpose, so the public only sees something released), run./deploy-prod.sh vX.Y.Z. It rebuildsdocs-site, restartsagentdeck-docs-static.service, and health-checks127.0.0.1:4321. - Report: Return the GitHub release URL.
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 · +4 lines 050532048343
- 2mo ago First seen · 62 lines · 29 tokens per session scan A 418c23d03d51
release is a skill published in the GitHub repository agentdecksdk/agentdeck (4 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,068 once invoked, about $0.0001 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-31.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
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…
port-to-github
Port an app or repo to GitHub from any source (git server, local folder, UNC share, Windows box over WinRM): all branches and tags, SHA-verified, CI translated, source-only history, deploy cut over with rollback. Use when the user says "move this app to GitHub", "port X to GitHub", "migrate from Gitea", "this app only…