work-flow-launch

work-flow-launch is a command for Claude Code from christopherlouet/claude-base. It costs 0 tokens per session (410 once invoked), scanned A, original, MIT.

A technical workflow for building and launching a product, from setting up the repository to monitoring the live service.

In plain words
What is it for?
Use it to configure a project, build and test an MVP, set up CI/CD, publish the product, and monitor it after launch.
Why use it?
It brings development, testing, accessibility, security, deployment, analytics, and launch tasks into one process.

Command for Claude Code

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 commands/christopherlouet/claude-base/work-flow-launch
Clone the repo
git clone --depth 1 https://github.com/christopherlouet/claude-base

Made for: Claude Code.

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 work-flow-launch

README.md
[![agentmods](https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-flow-launch.svg)](https://agentmods.dev/commands/christopherlouet/claude-base/work-flow-launch)
Your own site
<a href="https://agentmods.dev/commands/christopherlouet/claude-base/work-flow-launch"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-flow-launch.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 410 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00000 $0.00410
Opus 5 $0.00000 $0.00205
Sonnet 5 $0.00000 $0.00082
Haiku 4.5 $0.00000 $0.00041

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

Security

Grade A, and why

work-flow-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.

.claude/commands/work/work-flow-launch.md · 56 lines

What it actually says

WORK-FLOW-LAUNCH Agent

Technical workflow to develop and launch a product, from setup to go-live.

Context

$ARGUMENTS

Objective

Cover the technical workflow of product development and deployment. For the prior business analysis, use /biz:biz-launch. Prerequisites: business analysis completed, MVP defined, budget and timeline approved.

Workflow

Phase 1: Setup

  • Project setup and technical stack (repo, structure, linter, CI/CD, env vars)
  • CI/CD configuration and environments

Phase 2: Development

  • Core features per User Story (tests -> code -> review -> merge)
  • Tests and QA: unit > 80%, integration, critical E2E, security review
  • Responsive and accessibility

Phase 3: Launch

  • Optimized landing page (hero, CTA, social proof, pricing)
  • Analytics and SEO (events tracking, meta tags, sitemap, Core Web Vitals)
  • Go-live: domain, SSL, DNS, emails, payments, legal (ToS, Sales Terms, GDPR)
  • Post-launch monitoring: uptime, errors, performance, feedback

Expected output

  1. Setup: Project initialized with CI/CD
  2. MVP: Core features implemented and tested
  3. Launch: Product online with analytics and monitoring
Agent Usage
/biz:biz-launch Prior business analysis
/dev:dev-tdd Configure tests
/ops:ops-ci Advanced CI/CD
/qa:qa-security Security audit
/growth:growth-seo Advanced SEO

IMPORTANT: First do the business analysis with /biz:biz-launch before this workflow.

YOU MUST have legal in place before go-live (ToS, Sales Terms, GDPR).

NEVER sacrifice quality to move faster - better to postpone.

Think hard about what is truly MVP vs nice-to-have.

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 · 56 lines · 0 tokens per session scan A f73d66db3afa

Subscribe to this mod's changes

work-flow-launch is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 410 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.