agentmods.dev

release

release is a skill for Codex from kreek/consult. It costs 20 tokens per session (1,018 once invoked), scanned A, original, MIT.

A set of rules for preparing software releases, including version changes, notes, migrations, rollout plans, and rollback plans.

In plain words
What is it for?
Use it when preparing a release, updating a changelog, deciding version numbers, documenting breaking changes, or planning deployment and rollback steps.
Why use it?
It prevents release work from starting without a request or approval and keeps shared environments under human control.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

not rated 1repo changed 16d ago A scan 20 tokens original MIT

Good fit Use it when preparing a release, updating a changelog, deciding version numbers, documenting breaking changes, or planning deployment and rollback steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kreek/consult/release
View source ↗ kreek/consult
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.

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

Made for: Codex.

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

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/kreek/consult/release/github.svg)](https://agentmods.dev/skills/kreek/consult/release)
Your own site
<a href="https://agentmods.dev/skills/kreek/consult/release"><img src="https://agentmods.dev/badge/skills/kreek/consult/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/skills/kreek/consult/release"><img src="https://agentmods.dev/badge/skills/kreek/consult/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,018 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00020 $0.01018
Opus 5.5 $0.00008 $0.00407
Sonnet 5.5 $0.00004 $0.00204
Haiku 4.5 $0.00002 $0.00102

Measured 16d ago against content hash c112d59f282d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 16d 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.

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

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release

Iron Law

BREAKING CHANGES BUMP MAJOR. AGENTS PREPARE RELEASES; HUMANS MUTATE SHARED ENVIRONMENTS.

When to Use

  • The user asks for release prep, versioning, changelog, release notes, tags, publish planning, rollout, rollback, deprecation, or migration notes.
  • The user approves release prep after a concrete diff exposes release artifacts or rollout obligations.
  • A repo validator requires release artifact sync for an approved change.

When NOT to Use

  • Starting release work because a change might later need it. Note the risk in workflow and ask at the concrete release-prep decision point.
  • Triggering deploys, rollbacks, promotions, production config, flag flips, DNS, or infrastructure applies. Prepare the command or checklist for a human.
  • Database DDL safety; pair with database. Local bootstrap; use scaffolding.

Rules

  1. Release is a late gate. Implementation approval is not release approval.
  2. Agents prepare evidence, notes, checks, runbooks, and command plans. Humans run anything that mutates a shared environment, including staging config and feature flags. Report agent-run checks and human-run commands separately.
  3. Classify per release unit. In a monorepo, each library, CLI, plugin manifest, or container may have its own stream; lockstep bumps need repo policy or user approval. Use the higher plausible bump when compatibility is unclear.
  4. Release artifacts move together: manifests, committed lockfile, CHANGELOG entry, tag plan, dependency ranges, package metadata, publish order. Validate dependency resolution, dry-run packaging, and registry state before any tag plan.
  5. Ask before keeping lockfile or package-manager changes produced by a validation run.
  6. Prove a release script's scope matches the selected release units before trusting it to bump artifacts.
  7. Rollback must be faster than fix-forward and covers data, caches, config, and external side effects, not only code. Keep canary or progressive gates or name the equivalent.
  8. Feature flags default off and carry an owner, expiry, cleanup work, and a human-owned production change path. Kill-switches for existing behavior are the exception.

Read the full file on GitHub · 92 lines

Files

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.

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. 16d ago Changed c112d59f282d
  2. 1mo ago Changed · -42 lines 38eb00cfa0bb
  3. 1mo ago First seen · 134 lines · 20 tokens per session scan A c1697832d004

Subscribe to this mod's changes

release is a skill published in the GitHub repository kreek/consult (1 stars, last pushed 17d ago), licensed MIT. It adds 20 tokens to every session and 1,018 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.

Claude CodeGit and workflowReleasesagenticai-agentsclaude-code-pluginclaude-skillscodex-plugin
Related

Other skills, from other repositories

deploy-steward

Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.

SethGammon/Citadel · 56 tokens

release

CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.

oliver-kriska/claude-elixir-phoenix · 60 tokens

create-release-checklist

Create a release checklist and GitHub issue for an R package. Use when the user asks to "create a release checklist" or "start a release" for an R package.

posit-dev/skills · 41 tokens

han-release

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…

testdouble/han · 172 tokens

craft-plugin-release

Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist…

michtio/craftcms-claude-skills · 72 tokens

release

Cut a new release: group Conventional Commits since the last tag, append a CHANGELOG section, create a release commit, and add an annotated git tag. TRIGGER when the user says "cut a release", "tag a release", "release v1.2.0", "ship version 1.2.0", "create a release for 1.2.0", "bump the version to 1.2.0", "make a…

thettwe/nyann · 207 tokens