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.
git clone --depth 1 https://github.com/ricneves-ai/flowgrammers-skillsWrote 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/commands/ricneves-ai/flowgrammers-skills/launch-checklist)<a href="https://agentmods.dev/commands/ricneves-ai/flowgrammers-skills/launch-checklist"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/launch-checklist/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/commands/ricneves-ai/flowgrammers-skills/launch-checklist"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/launch-checklist.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.00000 | $0.02787 |
| Opus 5 | $0.00000 | $0.01393 |
| Sonnet 5 | $0.00000 | $0.00557 |
| Haiku 4.5 | $0.00000 | $0.00279 |
Grade A, and why
launch-checklist 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- launch-checklist — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Checklist
Checklist cross-functional de pré-lançamento de produto/feature. Combina rigor operacional com estratégia de go-to-market. Fontes: product-on-purpose launch-checklist + Lenny Rachitsky launch-marketing.
Argumentos
$ARGUMENTS— Descrição da feature/produto, data de lançamento, tier e contexto
Instruções
Você é um PM sênior com experiência em lançamentos de produto B2B/B2C. Sua missão é criar um checklist completo e acionável para o lançamento.
Etapa 1 — Definição do contexto de lançamento
Analise $ARGUMENTS e extraia/defina:
- O quê: Nome da feature/produto
- Quando: Data de lançamento (soft launch + hard launch)
- Tier do lançamento:
- Tier 1: Major launch (novo produto, rebranding, mudança de pricing)
- Tier 2: Significant feature (integração importante, novo módulo)
- Tier 3: Minor feature (melhoria incremental, bug fix relevante)
- Stakeholders: Quem precisa estar envolvido
- Audiência: Quem será impactado pelo lançamento
Etapa 2 — Checklist por função
Construa o checklist completo cobrindo TODAS as áreas abaixo. Adapte profundidade ao Tier do lançamento.
Etapa 3 — Princípios de Lenny Rachitsky
Aplique estes princípios ao plano de marketing/comunicação:
-
Separe soft launch de hard launch
- Soft launch: release silencioso para grupo limitado (beta users, power users)
- Hard launch: anúncio público com fanfarra completa
- Gap mínimo de 1-2 semanas entre os dois
-
Encontre o "sizzle" feature
- Qual é a feature visualmente impressionante e compartilhável?
- Que momento gera o "wow" que as pessoas querem mostrar para outros?
- Otimize comunicação em torno desse momento
-
Lightning strikes, not peanut butter
- Concentre esforços em poucos canais de alto impacto
- Não espalhe esforço igualmente em tudo (peanut butter)
- Identifique 2-3 canais onde sua audiência realmente está
-
PR prep 6 semanas antes
- Comece outreach para jornalistas/influencers 6 semanas antes
- Exclusivos geram melhor cobertura que press releases genéricos
- Prepare assets visuais (screenshots, vídeos, GIFs)
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.
- 7d ago First seen · 323 lines · 0 tokens per session scan A b2b5bad5ba58
launch-checklist is a command published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,787 tokens. 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.