agentmods.dev

release-deploy

release-deploy is a skill for Claude Code, Codex from afaraha8403/balakit. It costs 94 tokens per session (1,154 once invoked), scanned A, original, MIT.

A release workflow for publishing software through GitHub tags and GitHub Actions, which automate jobs after code is marked for release.

In plain words
What is it for?
It helps prepare beta releases from staging, production releases from main, version tags, release notes, and GitHub Releases.
Why use it?
It separates everyday commits from beta and production deployments and reduces mistakes when choosing a release channel.

Skill for Claude CodeCodex

not rated 1 7d ago A scan 94 tokens original MIT
View the source file afaraha8403/balakit
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/afaraha8403/balakit/release-deploy
Any agent
npx skills add afaraha8403/balakit --skill release-deploy
Clone the repo
git clone --depth 1 https://github.com/afaraha8403/balakit

Made for: Claude Code, 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-deploy

README.md
[![agentmods](https://agentmods.dev/badge/skills/afaraha8403/balakit/release-deploy.svg)](https://agentmods.dev/skills/afaraha8403/balakit/release-deploy)
Your own site
<a href="https://agentmods.dev/skills/afaraha8403/balakit/release-deploy"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/release-deploy.svg" alt="Measured on agentmods" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,154 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.00094 $0.01154
Opus 5 $0.00047 $0.00577
Sonnet 5 $0.00019 $0.00231
Haiku 4.5 $0.00009 $0.00115

Measured 4d ago against content hash 444d0bdf3a86, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

release-deploy 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 4d 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/skills/release-deploy/SKILL.md · 90 lines

How it starts

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

Release & Deploy (GitHub Tags)

Leading words: commits ≠ deploys; branch → channel; tag triggers ship; changelog is truth; interview once; never guess channel.

Core model

  • Commits ≠ deploys. Only a git tag + GitHub Release triggers deployment (via GitHub Actions or project-specific release jobs).
  • Branch → channel
    • main → production release
    • staging → beta release
  • Tags
    • Production: vMAJOR.MINOR.PATCH (e.g. v1.4.0)
    • Beta: vMAJOR.MINOR.PATCH-beta.N (e.g. v1.4.0-beta.1)
  • Release notes come from the project's maintained CHANGELOG.md (do not invent a changelog). See references/versioning.md.

Before every release

  1. Load project config
  2. Confirm channel with the user: beta (staging) or production (main). Never guess.
  3. Verify git state (PowerShell-safe; run as separate commands):
    • Correct branch checked out (staging or main)
    • Working tree clean (or user explicitly accepts dirty)
    • Branch is up to date with its remote
    • HEAD is the commit they intend to ship
  4. Determine next version from existing tags + user intent. Follow references/versioning.md.
  5. Extract notes from CHANGELOG.md for that version (or [Unreleased] if they are cutting that section into a version). If changelog is missing/ambiguous → stop and ask.

Release workflow

Follow references/gh-release.md. Summary:

  1. Ensure on the correct branch at the intended commit.
  2. Create annotated tag locally (optional if gh release create will create it).
  3. gh release create with tag, title, notes from changelog, and --target set to the branch (or SHA).
  4. Watch the project's release/deploy workflow (from project config) until green or report failure.
  5. Summarize: tag, release URL, channel, deploy target/URL from project config.

Read the full file on GitHub · 90 lines

Files

What ships with it

8 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. 4d ago First seen · 90 lines · 94 tokens per session scan A 444d0bdf3a86

Subscribe to this mod's changes

release-deploy is a skill published in the GitHub repository afaraha8403/balakit (1 stars, last pushed 7d ago), licensed MIT. It adds 94 tokens to every session and 1,154 once invoked, about $0.0005 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.

CI and CDDevOps and cloudGit and workflowProductionReleasesagent-rulesagent-skillsagents-mdai-agentsbetachangelogclaudedeploygithubreleasesemver
Related

Other skills, from other repositories

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/RuView · 27 tokens

Release Notes Generator

Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.

AgentEra/Agently · 46 tokens

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/ruflo · 27 tokens

ship

Ship a build — pre-flight checks, deploy, document, verify, monitor. Use when deploying code, publishing packages, or releasing.

martineserios/thebrana · 29 tokens

Release Engineering

Semantic versioning, changelog generation, and release/hotfix management so releases are predictable and reversible.

niels-emmer/myace · 24 tokens

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

proffesor-for-testing/agentic-qe · 27 tokens