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.
npx skills add peterblazejewicz/claude-plugins --skill shipping-and-launchgit clone --depth 1 https://github.com/peterblazejewicz/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/peterblazejewicz/claude-plugins/shipping-and-launch)<a href="https://agentmods.dev/skills/peterblazejewicz/claude-plugins/shipping-and-launch"><img src="https://agentmods.dev/badge/skills/peterblazejewicz/claude-plugins/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.
<a href="https://agentmods.dev/skills/peterblazejewicz/claude-plugins/shipping-and-launch"><img src="https://agentmods.dev/badge/skills/peterblazejewicz/claude-plugins/shipping-and-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00095 | $0.05024 |
| Opus 5 | $0.00048 | $0.02512 |
| Sonnet 5 | $0.00019 | $0.01005 |
| Haiku 4.5 | $0.00010 | $0.00502 |
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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 398 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 (ASP.NET Core service update, Blazor app revision, Avalonia/MAUI desktop release)
- Running an EF Core migration against a production database
- Publishing a new NuGet package version
- Opening a beta or early access program
- Any deployment that carries risk (all of them)
The Pre-Launch Checklist
Code Quality
- All tests pass (
dotnet testunit + integration, plus E2E if present) -
dotnet build -warnaserroris clean (no analyzer diagnostics suppressed by accident) -
dotnet format --verify-no-changesis clean - Code reviewed and approved
- No TODO comments that should be resolved before launch
- No
Debug.WriteLineor strayConsole.WriteLinedebugging statements in production code paths (useILogger<T>at the correct level) - No
[Fact(Skip = "…")]on tests that guard the behaviour you're shipping - Error handling covers expected failure modes;
OperationCanceledExceptionis not swallowed
Security
- No secrets in code,
appsettings.json, or git history -
dotnet list package --vulnerable --include-transitiveshows no Critical or High vulnerabilities (or documented allowlist entries with review dates) - Input validation on all user-facing endpoints (FluentValidation / DataAnnotations / MediatR pipeline)
-
[Authorize]/RequireAuthorization()on every endpoint except explicitly-public ones - Security headers configured (CSP, HSTS,
X-Content-Type-Options,X-Frame-Options) - Rate limiting on authentication endpoints (
AddFixedWindowLimiter) - CORS configured to specific origins (not
AllowAnyOrigin()with credentials) - ASP.NET Core Data Protection key ring is persisted and shared across instances (Azure Key Vault, Redis, or file share)
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.
- 10d ago First seen · 398 lines · 95 tokens per session scan A 410eecbf5598
shipping-and-launch is a skill published in the GitHub repository peterblazejewicz/claude-plugins (7 stars, last pushed 2mo ago), licensed MIT. It adds 95 tokens to every session and 5,024 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.
Other skills, from other repositories
azure-validate
WORKFLOW SKILL — Pre-deployment validation for Azure: config, infrastructure (Bicep/Terraform), permissions, prerequisites. WHEN: 'validate my app', 'check deployment readiness', 'run preflight checks', 'validate azure.yaml', 'validate Bicep', 'test before deploying', 'validate Azure Functions'. DO NOT USE FOR…
azure-deploy
WORKFLOW SKILL — Execute Azure deployments (azd up, azd deploy, terraform apply) for already-prepared apps with built-in error recovery. WHEN: 'run azd up', 'run azd deploy', 'push to production', 'go live', 'bicep deploy', 'terraform apply', 'publish to Azure'. DO NOT USE FOR: creating new apps (azure-prepare)…
iac-common
UTILITY SKILL — Shared IaC deploy patterns for Bicep + Terraform agents: deployment strategies, circuit breaker, known deploy issues. WHEN: "phased deployment", "circuit breaker", "deploy strategy", "deploy issue", "shared IaC pattern". DO NOT USE FOR: preflight (azure-validate), code generation (azure-bicep-patterns…
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
gsap-core
Official GSAP skill for the core API — gsap.to(), from(), fromTo(), easing, duration, stagger, defaults, gsap.matchMedia() (responsive, prefers-reduced-motion). Use when the user asks for a JavaScript animation library, animation in React/Vue/vanilla, GSAP tweens, easing, basic animation, responsive or reduced-motion…