release

release is a skill for Claude Code, Codex from Mburdo/knowledge_and_vibes. It costs 30 tokens per session (2,542 once invoked), scanned A, original, MIT.

A final checklist for checking whether coding work is ready to ship. It reviews tasks, tests, security, version-control status, and recent commits before production deployment.

In plain words
What is it for?
Running release checks with Beads, scanning staged code for security issues, running pytest or npm test, and reviewing Git status and history.
Why use it?
It catches unfinished work, blocked tasks, security problems, failing tests, and uncommitted changes before release.

Skill for Claude CodeCodex

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/mburdo/knowledge_and_vibes/release
Any agent
npx skills add Mburdo/knowledge_and_vibes --skill release
Clone the repo
git clone --depth 1 https://github.com/Mburdo/knowledge_and_vibes

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/release.svg)](https://agentmods.dev/skills/mburdo/knowledge_and_vibes/release)
Your own site
<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/release"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/release.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,542 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.00030 $0.02542
Opus 5 $0.00015 $0.01271
Sonnet 5 $0.00006 $0.00508
Haiku 4.5 $0.00003 $0.00254

Measured 4d ago against content hash b4c450722e26, 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 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.

.claude/skills/release/SKILL.md · 388 lines

How it starts

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

Release — Pre-Ship Gate

Final verification before shipping. Maps to Protocol P12 (Release Readiness) and P13 (Security Gate).

Pattern: This skill runs after all beads are closed. It verifies all work is done, security is clean, and the system is ready to ship.

When This Applies

Signal Action
All beads closed Run release checklist
User says "/release" or "ship" Run release checklist
Before production deployment Run release checklist

Prerequisites

Before running /release:

  1. All execution phases complete (or user explicitly skipping)
  2. No beads in in_progress status
  3. Agent Mail available (if multi-agent)

Tool Reference

Verification Commands

Command Purpose
bd list --json Verify all beads closed
bv --robot-summary Check for orphaned/blocked beads
bv --robot-alerts Surface any issues
ubs --staged Security scan (MANDATORY)
pytest / npm test Run test suite
git status Check for uncommitted changes
git log --oneline -10 Recent commit history

Agent Mail (MCP)

Tool Purpose
fetch_inbox(agent_name, urgent_only=True) Check for unresolved urgent messages
release_file_reservations(project_key, agent_name) Release any held reservations
send_message(subject="[RELEASE READY]") Announce release readiness

Message Subjects

Pattern When
[RELEASE READY] Project Name All checks passed
[RELEASE BLOCKED] Project Name Blockers found

Architecture

┌─────────────────────────────────────────────────────────────────┐
│                      RELEASE ORCHESTRATOR                        │
│  You are here. You:                                              │
│  - Verify all beads closed                                       │
│  - Run security scan                                             │
│  - Check for uncommitted work                                    │
│  - Validate against rigor tier                                   │
│  - Generate release report                                       │
└─────────────────────────────────────────────────────────────────┘
                              │
         ┌────────────────────┼────────────────────┐
         │                    │                    │
         ▼                    ▼                    ▼
┌─────────────────┐  ┌─────────────────┐  ┌─────────────────┐
│  Bead Status    │  │  Security Gate  │  │  Multi-Agent    │
│  bd list        │  │  ubs --staged   │  │  Cleanup        │
│  bv --robot-*   │  │  Language audits│  │  Agent Mail     │
└─────────────────┘  └─────────────────┘  └─────────────────┘
         │                    │                    │
         └────────────────────┼────────────────────┘
                              │
                              ▼
                    ┌─────────────────┐
                    │  Release Report │ → Present to operator
                    │  GO / NO-GO     │
                    └─────────────────┘

Read the full file on GitHub · 388 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. 4d ago First seen · 388 lines · 30 tokens per session scan A b4c450722e26

Subscribe to this mod's changes

release is a skill published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 8mo ago), licensed MIT. It adds 30 tokens to every session and 2,542 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

openai/symphony · 42 tokens

changelog-entry

Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".

telepresenceio/telepresence · 60 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens

release-helper

Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.

Sahir619/fable-method · 43 tokens