agentmods.dev

shipping-and-launch

shipping-and-launch is a skill for Claude Code, Cursor from mamahoos/dot-files. It costs 45 tokens per session (2,608 once invoked), scanned A, a copy of shipping-and-launch, MIT.

A release-preparation guide for putting software into production, the environment used by real users. It covers checks for code, security, monitoring, staged rollout, and rollback.

In plain words
What is it for?
Use it to prepare launch checklists, verify builds and tests, configure monitoring, plan gradual releases, and define rollback procedures.
Why use it?
It reduces the chance that a deployment will fail silently, expose a vulnerability, or leave you without a safe way to undo the change.

Skill for Claude CodeCursor

Written for Claude Code and Cursor: disable-model-invocation in frontmatter, but also installed under .cursor/.

not rated 4repo changed 2d ago A scan 45 tokens copy · 100% MIT

Good fit Use it to prepare launch checklists, verify builds and tests, configure monitoring, plan gradual releases, and define rollback procedures.

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

Made for: Claude Code, Cursor.

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/mamahoos/dot-files/shipping-and-launch/github.svg)](https://agentmods.dev/skills/mamahoos/dot-files/shipping-and-launch)
Your own site
<a href="https://agentmods.dev/skills/mamahoos/dot-files/shipping-and-launch"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/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/mamahoos/dot-files/shipping-and-launch"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/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,608 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 100% 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.02608
Opus 5 $0.00023 $0.01304
Sonnet 5 $0.00009 $0.00522
Haiku 4.5 $0.00005 $0.00261

Measured 2d ago against content hash 0f522c6bbe4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 2d 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

100% identical to shipping-and-launch — 1 line 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.

home/.cursor/skills/shipping-and-launch/SKILL.md · 332 lines

How it starts

The opening of the file, as written. The whole thing — 332 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
  • The ecosystem's dependency audit (npm audit, pip-audit, cargo 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

Read the full file on GitHub · 332 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. 2d ago Changed · +20 lines 0f522c6bbe4e
  2. 8d ago First seen · 312 lines · 45 tokens per session scan A 33c83952d869

Subscribe to this mod's changes

shipping-and-launch is a skill published in the GitHub repository mamahoos/dot-files (4 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 2,608 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to shipping-and-launch, differing in 1 line, and is treated as a copy.

DevOps and cloudGit and workflowReleasesbashconfigurationdotfiles
Related

Other skills, from other repositories

npm-release

Guide for setting up automated npm package releases via GitHub Actions using Trusted Publishing (OIDC). Use when creating release workflows, publishing to npm, or troubleshooting CI/CD publish failures.

OzzyCzech/dotfiles · 39 tokens

gitlab-cli

Reference guide for GitLab CLI (glab) commands. Use when running glab commands for issues, merge requests, pipelines, releases, or CI/CD operations, or when the user asks about GitLab CLI syntax.

OzzyCzech/dotfiles · 48 tokens

git-commit

This skill should be used BEFORE running any git commit command. Triggers when about to run git commit. Ensures commit messages follow Conventional Commits specification and prompts for the Jira ticket number.

fredrikaverpil/dotfiles · 43 tokens

fj

Forgejo CLI for issues, pull requests, repositories, releases, Actions, organizations, and users on git.natsukium.com. Use whenever a request references git.natsukium.com or a Git remote hosted there; this is the Forgejo counterpart to the gh skill.

natsukium/dotfiles · 58 tokens

mbo-plan

Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…

sfc-gh-eraigosa/dotfiles · 260 tokens

wispr-flow-debug

Debug and test the Wispr Flow AutoHotkey dictation triggers (Copilot key + extra keys) from WSL by deploying macos.ahk to the Windows Desktop, reloading AutoHotkey, and reading the debug log. Use when an activation/trigger key isn't starting/stopping dictation, when the overlay clicks land wrong, or when verifying a…

sfc-gh-eraigosa/dotfiles · 87 tokens