agentmods.dev

release

A release procedure for the agentdeck project. It covers version updates, changelog entries, pull requests, branch promotion, tags, and required checks.

In plain words
What is it for?
It is for bumping a semantic version, updating CHANGELOG.md, merging dev into main, creating a vX.Y.Z tag, and verifying the release preconditions.
Why use it?
It reduces mistakes when preparing a release, such as using the wrong branch, leaving issues open, or publishing with failing checks.

Skill for Claude CodeCodex

2 2d ago A scan 29 tokens original MIT
View the source file agentdecksdk/agentdeck
Install

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.

agentmods
npx agentmods add skills/agentdecksdk/agentdeck/release
Any agent
npx skills add agentdecksdk/agentdeck --skill release
Clone the repo
git clone --depth 1 https://github.com/agentdecksdk/agentdeck

Made for: Claude Code, Codex.

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 996 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00996
Opus 5 $0.00015 $0.00498
Sonnet 5 $0.00006 $0.00199
Haiku 4.5 $0.00003 $0.00100

Measured yesterday against content hash 418c23d03d51, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.agents/skills/release/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 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

  1. Version: Confirm SemVer bump (pyproject.toml and CHANGELOG.md).
  2. Preflight: Verify clean working tree, non-empty [Unreleased] section, and make check is 100% green. Run it unpiped (make check, not make check | tail) so its own exit code is what you read; a pipe reports the last command's status, not the gate's.
  3. Bump issue: python scripts/release_bump.py issues X.Y.Z creates (or reuses) the vX.Y.Z milestone, assigns it to every issue Fixes/Closes-referenced since the last tag, opens the labeled chore: cut and ship vX.Y.Z issue, and prints its number.
  4. Bump PR into dev:
    • python scripts/release_bump.py bump X.Y.Z updates pyproject.toml's version and moves CHANGELOG.md's [Unreleased] entries to a dated ## [X.Y.Z] heading with compare links.
    • Run python scripts/generate_docs_reference.py once, then verify python scripts/generate_docs_reference.py --check.
    • Commit: chore(release): vX.Y.Z. Open the PR against the bump issue from step 3 (Closes #N), wait for every required check, merge.
  5. Promotion issue: python scripts/release_bump.py promote X.Y.Z opens the labeled chore: release vX.Y.Z to main issue in the same milestone and prints its number.
  6. Promotion PR, dev to main: Open it against the promotion issue from step 5 (Refs #N). Issue hygiene, slop, and Check affected documentation skip themselves on a main-based PR: each already ran the real per-PR version of itself against dev at merge time, and this diff is the whole release cycle re-evaluated, not a new change. Wait for check and Build documentation, then merge and close the promotion issue by hand.
  7. Tag: git tag vX.Y.Z && git push origin vX.Y.Z. release.yml publishes to PyPI on this push; there is no undo once the tag lands.
  8. 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.0 through v5.1.0 all shipped with 0 open issues but stayed open on GitHub.
  9. 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 rebuilds docs-site, restarts agentdeck-docs-static.service, and health-checks 127.0.0.1:4321.
  10. Report: Return the GitHub release URL.

Read the full file on GitHub · 62 lines

Changes

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.

  1. yesterday First seen · 62 lines · 29 tokens per session scan A 418c23d03d51

Subscribe to this mod's changes

release is a skill published in the GitHub repository agentdecksdk/agentdeck (2 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 996 once invoked, about $0.0001 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.

Git and workflowagent-frameworkagent-observabilityagent-runtimeagent-workflowsagentic-aiai-agents
Related

Other skills, from other repositories

png-press

Teaches agents how to author content and configure writepng so PNGs render at the correct size, with tight cropping, readable text, and consistent scaling.

kdcube/kdcube · 36 tokens

bundle-builder

Build or repair KDCube bundles. Use the KDCube bundle docs, the workspace reference bundle, and the shared bundle suite before writing code.

kdcube/kdcube · 30 tokens

sources-section

Appends a Sources/References section using only web sources from the sources pool.

kdcube/kdcube · 19 tokens

local-runtime

Start local KDCube, reload one bundle, stop the local runtime, or run the shared bundle suite.

kdcube/kdcube · 22 tokens

bootstrap-local

Generate a clean local descriptor set for one KDCube bundle and print the exact next commands to start it.

kdcube/kdcube · 22 tokens

automations

Create, inspect, edit, archive, delete, run, and search scheduled or executable automation assets.

kdcube/kdcube · 23 tokens