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 agentmods add skills/impactbrussels/founderos/launch-plannpx skills add impactbrussels/FounderOS --skill launch-plangit clone --depth 1 https://github.com/impactbrussels/FounderOSWrote 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/impactbrussels/founderos/launch-plan)<a href="https://agentmods.dev/skills/impactbrussels/founderos/launch-plan"><img src="https://agentmods.dev/badge/skills/impactbrussels/founderos/launch-plan.svg" alt="Measured on agentmods" 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 | $0.00128 | $0.01269 |
| Opus 5 | $0.00064 | $0.00634 |
| Sonnet 5 | $0.00026 | $0.00254 |
| Haiku 4.5 | $0.00013 | $0.00127 |
Grade A, and why
launch-plan 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 3d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Plan
First-time founders treat "launch" as a single fireworks moment: press the button, hope the internet shows up. It almost never does. A launch is a sequence - built on an audience you warmed up beforehand, aimed at one measurable outcome, and followed by a review that turns the day into learning. This skill replaces the one-shot gamble with a plan you can execute and repeat.
The method
Built on the Founder OS scaffold (High tier). Full templates in references/launch-checklist.md.
Step 1 - Define the launch goal and the ONE metric
A launch is not "tell people we exist." Pick a single outcome that proves the launch worked:
sign-ups, waitlist adds, first paying customers, demo bookings, or upvotes/ranking on a platform.
Translate [GOAL] into one number - the [METRIC] - and set the bar that counts as success
before the day. Everything else is vanity. One metric keeps the team aimed.
Step 2 - Choose the launch type
Match the type to your stage and audience, not to what looks impressive (menu in references):
quiet beta (a handful of hand-picked users), waitlist (build demand before the product),
public launch (you have an audience to mobilise), or platform launch (a directory,
marketplace, app store, or Product-Hunt-style listing where buyers already gather). Each has a
different prep and a different [METRIC]. Don't do a public launch with no audience - that's the
classic failure (see Step 5).
Step 3 - Build the asset list
Work backward from the launch type to the assets you actually need (checklist in references):
landing page, demo/video, launch copy (post, thread, email), FAQ, an outreach list of warm
contacts, and the tracking to read [METRIC]. Cut anything that doesn't serve the one goal.
Don't build a press kit for a quiet beta. A draft asset is not a shipped asset - batch them,
review the whole set once, then finalize.
Step 4 - Sequence the T-minus timeline
A launch has three phases: pre (warm the audience, collect the list, line up supporters),
during (the choreographed launch-day run of show - what posts when, who amplifies, how you
respond), and post (follow-up, thank-yous, converting attention into the [METRIC]). Use the
T-minus template in references. The pre-phase is where launches are won; if your audience is cold
on launch day, you've already lost.
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.
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.
- 3d ago First seen · 90 lines · 128 tokens per session scan A a2f11b1a3748
launch-plan is a skill published in the GitHub repository impactbrussels/FounderOS (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 128 tokens to every session and 1,269 once invoked, about $0.0006 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
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
metrics-instrumentation
Specification for instrumenting an opik-backend workflow with operational OpenTelemetry metrics — per-stage throughput/latency/error counters and native histograms, dimensioned per-customer (workspace). Use when a pipeline (scoring, ingestion, experiments, jobs) needs per-stage visibility. Covers metric emission only…
review-agents-md
Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.
chat-complex-documents
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready…
experiment-tracking-swanlab
Provides guidance for experiment tracking with SwanLab. Use when you need open-source run tracking, local or self-hosted dashboards, and lightweight media logging for ML workflows.