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 oleg494/coding-kit --skill shipping-and-launchgit clone --depth 1 https://github.com/oleg494/coding-kitWrote 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/oleg494/coding-kit/shipping-and-launch)<a href="https://agentmods.dev/skills/oleg494/coding-kit/shipping-and-launch"><img src="https://agentmods.dev/badge/skills/oleg494/coding-kit/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/oleg494/coding-kit/shipping-and-launch"><img src="https://agentmods.dev/badge/skills/oleg494/coding-kit/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.00045 | $0.00933 |
| Opus 5.5 | $0.00018 | $0.00373 |
| Sonnet 5.5 | $0.00009 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00093 |
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 yesterday.
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipping and Launch
Overview
Ship with confidence. 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
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
console.logdebugging statements in production code - Error handling covers expected failure modes
Security
- No secrets in code or version control
- Dependency 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
Performance
- Core Web Vitals within "Good" thresholds
- No N+1 queries in critical paths
- Images optimized
- Bundle size within budget
- Database queries have appropriate indexes
Infrastructure
- Environment variables set in production
- Database migrations applied
- DNS and SSL configured
- Health check endpoint exists and responds
- Logging and error reporting configured
Feature Flag Strategy
Ship behind feature flags to decouple deployment from release:
1. DEPLOY with flag OFF → Code in production but inactive
2. ENABLE for team/beta → Internal testing in production
3. GRADUAL ROLLOUT → 5% → 25% → 50% → 100%
4. MONITOR at each stage → Watch error rates, latency, feedback
5. CLEAN UP → Remove flag within 2 weeks of full rollout
Rules:
- Every feature flag has an owner and expiration date
- Clean up flags within 2 weeks of full rollout
- Don't nest feature flags
- Test both flag states in CI
Staged Rollout
1. DEPLOY to staging → full test suite + manual smoke test
2. DEPLOY to production (flag OFF) → verify health check, error monitoring
3. ENABLE for team (24h monitoring window)
4. CANARY rollout (5% of users) → 24-48h monitoring
5. GRADUAL increase (25% → 50% → 100%)
6. FULL rollout → monitor 1 week → clean up flag
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.
- yesterday Changed cb5638584a67
- 7d ago Changed 97f5783cfaac
- 14d ago Changed 57c1b260f4e2
- 16d ago Changed 1616da366b4b
- 1mo ago Changed 2f163793e9cf
- 1mo ago Changed 57ead1c48619
- 1mo ago Changed b842e1050a8e
- 1mo ago Changed 7737354d4f19
- 1mo ago Changed cd0e3407663a
- 1mo ago First seen · 112 lines · 45 tokens per session scan A 716a7c3dabfb
shipping-and-launch is a skill published in the GitHub repository oleg494/coding-kit (3 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 933 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.
Other skills, from other repositories
dsh-plugin-publisher
A release tool for DSH plugins, where DSH is the DeepSeek Harness used to load these add-ons. It validates an existing plugin package, publishes it through npm, Git, or a tarball, and checks that the harness can load it.
lov-skill-optimizer
Audit and optimize one or more existing Agent Skills from a canonical source path, then bump semver, update README/SKILL.md/skill.yaml/CHANGELOG.md, and verify installed copies and catalog synchronization. Checks frontmatter, trigger quality, CLI hygiene, naming, portability, version drift, dirty worktrees, shared…
lov-skill-publisher
Publish or submit a validated Skill. Default to the LovStudio official website, run lov-skill-pricing automatically, and use other channels only when explicitly named.
lov-app-delta-updater
An automatic update workflow for Tauri and Electron desktop apps. It distinguishes signed full packages from genuine delta packages, which contain only changes, and checks how updates are discovered, installed, verified, and recovered.
github-release-notes-writer
Draft or update user-focused GitHub Release Notes from verified tags, commits, pull requests, existing releases, and supplied changelog baselines. Use when preparing prerelease or stable release notes, turning GitHub's generated What's Changed list into a curated narrative, documenting upgrades or breaking changes, or…
github-release-pr-writer
Draft or update GitHub release pull request descriptions from verified tags, commits, merged pull requests, and the release diff. Use when a PR prepares a version, aligns release metadata, promotes a prerelease, or needs a reviewer-focused release summary, exact change inventory, breaking-change section, or migration…