agentmods.dev

shipping-and-launch

shipping-and-launch is a skill for Claude Code from Goktug/ai-crew. It costs 45 tokens per session (2,294 once invoked), scanned A, a copy of shipping-and-launch, MIT.

A launch-planning guide for putting software, data changes, or infrastructure into production, where real users and systems depend on them. It covers checks before release, monitoring, staged rollouts, and plans for reversing a change.

In plain words
What is it for?
Use it to create a pre-launch checklist, verify tests and security checks, set up monitoring, define success criteria, plan a gradual rollout, and prepare a rollback strategy.
Why use it?
It reduces the risk of releasing broken, insecure, or hard-to-reverse changes without knowing how to detect and handle problems.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ai-crew plugin — 24 skills, 8 commands, 7 agents, 1 hook shipped together

not rated 6repo 2mo ago A scan 45 tokens copy · 83% MIT

Good fit Use it to create a pre-launch checklist, verify tests and security checks, set up monitoring, define success criteria, plan a gradual rollout, and prepare a rollback strategy.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/goktug/ai-crew/shipping-and-launch
View source ↗ Goktug/ai-crew
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 Goktug/ai-crew --skill shipping-and-launch
Clone the repo
git clone --depth 1 https://github.com/Goktug/ai-crew

Made for: Claude Code.

Or install ai-crew, the plugin that ships this one along with the rest of its 24 skills, 8 commands, 7 agents, 1 hook.

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 shipping-and-launch

README.md
[![agentmods](https://agentmods.dev/badge/skills/goktug/ai-crew/shipping-and-launch/github.svg)](https://agentmods.dev/skills/goktug/ai-crew/shipping-and-launch)
Your own site
<a href="https://agentmods.dev/skills/goktug/ai-crew/shipping-and-launch"><img src="https://agentmods.dev/badge/skills/goktug/ai-crew/shipping-and-launch/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 shipping-and-launch

Your own site · 80×15
<a href="https://agentmods.dev/skills/goktug/ai-crew/shipping-and-launch"><img src="https://agentmods.dev/badge/skills/goktug/ai-crew/shipping-and-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,294 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 83% copy Near-identical to another mod 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.00045 $0.02294
Opus 5 $0.00023 $0.01147
Sonnet 5 $0.00009 $0.00459
Haiku 4.5 $0.00005 $0.00229

Measured 12d ago against content hash 3e54575e5dcd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

shipping-and-launch 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 12d 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.

Origin

This is a copy

83% identical to shipping-and-launch — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/shipping-and-launch/SKILL.md · 310 lines

How it starts

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

Shipping and Launch

Overview

Ship with confidence. The goal is not just to deploy — it's to deploy safely, with monitoring in place, a rollback plan ready, and a clear understanding of what success looks like. Every launch should be reversible, observable, and incremental.

When to Use

  • Deploying a feature to production for the first time
  • Releasing a significant change to users
  • Migrating data or infrastructure
  • Opening a beta or early access program
  • Any deployment that carries risk (all of them)

The Pre-Launch Checklist

Code Quality

  • All tests pass (unit, integration, e2e)
  • Build succeeds with no warnings
  • Lint and type checking pass
  • Code reviewed and approved
  • No TODO comments that should be resolved before launch
  • No console.log debugging statements in production code
  • Error handling covers expected failure modes

Security

  • No secrets in code or version control
  • npm audit shows no critical or high vulnerabilities
  • Input validation on all user-facing endpoints
  • Authentication and authorization checks in place
  • Security headers configured (CSP, HSTS, etc.)
  • Rate limiting on authentication endpoints
  • CORS configured to specific origins (not wildcard)

Performance

  • Core Web Vitals within "Good" thresholds
  • No N+1 queries in critical paths
  • Images optimized (compression, responsive sizes, lazy loading)
  • Bundle size within budget
  • Database queries have appropriate indexes
  • Caching configured for static assets and repeated queries

Accessibility

  • Keyboard navigation works for all interactive elements
  • Screen reader can convey page content and structure
  • Color contrast meets WCAG 2.1 AA (4.5:1 for text)
  • Focus management correct for modals and dynamic content
  • Error messages are descriptive and associated with form fields
  • No accessibility warnings in axe-core or Lighthouse

Infrastructure

  • Environment variables set in production
  • Database migrations applied (or ready to apply)
  • DNS and SSL configured
  • CDN configured for static assets
  • Logging and error reporting configured
  • Health check endpoint exists and responds

Read the full file on GitHub · 310 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. 12d ago First seen · 310 lines · 45 tokens per session scan A 3e54575e5dcd

Subscribe to this mod's changes

shipping-and-launch is a skill published in the GitHub repository Goktug/ai-crew (6 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 2,294 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to shipping-and-launch, differing in 31 lines, and is treated as a copy.

DevOps and cloud
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens