A deployment workflow with three stages: checks before release, the deployment itself, and verification afterward, including rollback planning.

Use it when asked to ship, release, or deploy software, or when checking whether a deployment succeeded and deciding how to roll it back.

It makes release risks visible and requires approval before actions that change shared or production systems.

ship — Skill for Claude Code by baleen37/bstack

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 baleen37/bstack --skill ship

Clone the repo

git clone --depth 1 https://github.com/baleen37/bstack

Made for: Claude Code.

Or install me, the plugin that ships this one along with the rest of its 10 skills, 1 agent, 7 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/baleen37/bstack/ship/github.svg)](https://agentmods.dev/skills/baleen37/bstack/ship)

Your own site

<a href="https://agentmods.dev/skills/baleen37/bstack/ship"><img src="https://agentmods.dev/badge/skills/baleen37/bstack/ship/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/baleen37/bstack/ship"><img src="https://agentmods.dev/badge/skills/baleen37/bstack/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,675 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.

Model	Per session	Once invoked
Fable 5.1	$0.00060	$0.01675
Opus 5.5	$0.00024	$0.00670
Sonnet 5.5	$0.00012	$0.00335
Haiku 4.5	$0.00006	$0.00168

Measured 1mo ago against content hash d71c2ccf7e84, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/me/skills/ship/SKILL.md · 153 lines

How it starts

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

Ship

Automation Policy

Run safe read-only checks and local reversible work automatically (git/CI status, tests, lint, audits, drafting rollout/rollback plans). Classify each finding AUTO-COMPLETED, NEEDS_APPROVAL, BLOCKED, or READY_FOR_SHIP_REVIEW.

Ask for approval before anything that changes shared or external state: pushes, PR creation/merge, releases, deploys, infra/flag/config/secret/DB changes, external notifications, rollbacks, destructive commands, data migrations.

Execution Workflow

Three phases: pre-deploy → deploy → post-deploy. Do not skip phases.

First, classify the change:

Deployable (touches code/infra that runs in production) → full three-phase flow.
Non-deployable (docs, skills, internal scripts, CI config without runtime effect) → run Phase 1 checks (tests/lint relevant to the change), commit/PR per normal flow, skip Phases 2–3. State explicitly: "Non-deployable change, skipping deploy/verify phases."

If unsure, ask the user once. Don't invent a deploy step for a doc change.

Phase 1 — Pre-deploy

Identify scope — launch type, changed files, blast radius, production systems touched.
Read the deploy convention — see "Reading Deploy Convention" below. If the project has none, ask once and offer to record the answer.
Run checks — local verification (tests, lint, type, build), CI/PR status, dependency/security audits, docs.
Draft artifacts — rollout stages, rollback triggers/procedure, monitoring targets, owners, post-deploy checks.
Classify and decide — mark each item AUTO-COMPLETED, NEEDS_APPROVAL, BLOCKED, or READY_FOR_SHIP_REVIEW. Stop and report evidence if anything is BLOCKED. Present GO/NO-GO with the rollback plan.

Phase 2 — Deploy

Execute deploy — run the command from the deploy convention. This is NEEDS_APPROVAL; never run without the user's explicit go-ahead.

Phase 3 — Post-deploy

Verify — run the checks from "Post-Deploy Verification" below.
On failure — collect evidence, draft the rollback command from the deploy convention, present as NEEDS_APPROVAL. Do not auto-rollback.
Report — what shipped, what was verified, what to watch.

Read the full file on GitHub · 153 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.

1mo ago Changed d71c2ccf7e84
1mo ago Changed · -47 lines acbbd4411613
1mo ago Changed 007b7910a14f
1mo ago First seen · 200 lines · 60 tokens per session scan A 49ede3f288be

Subscribe to this mod's changes

ship is a skill published in the GitHub repository baleen37/bstack (4 stars, last pushed 18d ago), licensed MIT. It adds 60 tokens to every session and 1,675 once invoked, about $0.0002 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.

DevOps and cloud Git and workflow Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

release

Fully automate a release with version-bump and childhood.

thedotmack/claude-mem · 13 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

ship