launch

A plan for releasing a product, feature, or update and getting it into users' hands. It covers stages such as beta access, waitlists, announcements, and launch promotion.

In plain words
What is it for?
Use it to plan SaaS launches, feature releases, Product Hunt launches, early-access programs, and go-to-market work.
Why use it?
It helps teams treat a release as an ongoing process of gathering feedback and building attention, rather than as one announcement.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/patrickserrano/lacquer/launch
Any agent
npx skills add patrickserrano/lacquer --skill launch
Clone the repo
git clone --depth 1 https://github.com/patrickserrano/lacquer

Made for: Claude Code, Codex.

Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,258 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00124 $0.03258
Opus 5 $0.00062 $0.01629
Sonnet 5 $0.00025 $0.00652
Haiku 4.5 $0.00012 $0.00326

Measured yesterday against content hash 1d5f5e6a4caa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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.

Origin

This is a copy

100% identical to launch — 0 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.

core/skills/launch/SKILL.md · 382 lines

How it starts

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

Launch Strategy

You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.

A strong launch isn't about a single moment. It's about:

  • Getting your product into users' hands early
  • Learning from real feedback
  • Making a splash at every stage
  • Building momentum that compounds over time

The ORB Framework

Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.

Owned Channels

You own the channel (though not the audience). Direct access without algorithms or platform rules.

Examples:

  • Email list
  • Blog
  • Podcast
  • Branded community (Slack, Discord)
  • Website/product

Why they matter:

  • Get more effective over time
  • No algorithm changes or pay-to-play
  • Direct relationship with audience
  • Compound value from content

Start with 1-2 based on audience:

  • Industry lacks quality content → Start a blog
  • People want direct updates → Focus on email
  • Engagement matters → Build a community

Example - Superhuman: Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.

Rented Channels

Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.

Read the full file on GitHub · 382 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. yesterday First seen · 382 lines · 124 tokens per session scan A 1d5f5e6a4caa

Subscribe to this mod's changes

launch is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed 2d ago), licensed MIT. It adds 124 tokens to every session and 3,258 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to launch, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

install-mimi-remote

安装、配置、配对、迁移、升级、诊断、回滚或卸载 Mimi Remote;在 macOS 上安装和维护 Mimi Remote Mac 菜单栏 App / DMG,或通过 Homebrew、Linux user-systemd 部署 agentd;从源码构建 iPhone/iPad App;配置 Codex 主通道和可选 Claude Code 实验 Runtime。用户提出“安装 Mimi Remote”“安装或修复 Mac 菜单栏 App”“在 iPad/iPhone 上使用 Codex 或 Claude Code”“部署、迁移或修复 agentd”“升级、回滚、卸载 Mimi Remote”“构建 MimiRemote iOS…

gaixianggeng/mimi-remote · 162 tokens

install-mimi-remote

安装、配置、配对、迁移、升级、诊断、回滚或卸载 Mimi Remote;在 macOS 上安装和维护 Mimi Remote Mac 菜单栏 App / DMG,或通过 Homebrew、Linux user-systemd 部署 agentd;从源码构建 iPhone/iPad App;配置 Codex 主通道和可选 Claude Code 实验 Runtime。用户提出“安装 Mimi Remote”“安装或修复 Mac 菜单栏 App”“在 iPad/iPhone 上使用 Codex 或 Claude Code”“部署、迁移或修复 agentd”“升级、回滚、卸载 Mimi Remote”“构建 MimiRemote iOS…

gaixianggeng/mimi-remote · 162 tokens

flutter-cherry-pick

How to land a formal cherry-pick of a merged PR for the flutter/flutter repo stable or beta channel. Only use for flutter/flutter landed pull requests. Only use when the cherry pick request is into "stable", "beta" or a branch that has the format with flutter- . -candidate.0.

flutter/flutter · 72 tokens

upgrade-browser

Upgrade browser versions (Chrome or Firefox) in the Flutter Web Engine and/or Framework tests. Use when asked to roll or upgrade Chrome or Firefox to a newer version.

flutter/flutter · 36 tokens

run-devicelab-with-led

Run DeviceLab tests for Flutter PRs using LUCI's led CLI tool. Use when asked to run, launch, try, or deflake a post-submit or devicelab test against a PR using led.

flutter/flutter · 55 tokens

natural-writing

Contains well-defined rules for creating natural, accurate, and readable writing. Use whenever authoring longer text, like analysis documents, PR or CL descriptions, or documentation.

flutter/flutter · 36 tokens