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/tonypls/agentic-product-launch/launch-projectnpx skills add tonypls/agentic-product-launch --skill launch-projectgit clone --depth 1 https://github.com/tonypls/agentic-product-launchWrote 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/tonypls/agentic-product-launch/launch-project)<a href="https://agentmods.dev/skills/tonypls/agentic-product-launch/launch-project"><img src="https://agentmods.dev/badge/skills/tonypls/agentic-product-launch/launch-project.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.1 | $0.00126 | $0.00926 |
| Opus 5 | $0.00063 | $0.00463 |
| Sonnet 5 | $0.00025 | $0.00185 |
| Haiku 4.5 | $0.00013 | $0.00093 |
Grade A, and why
launch-project 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 6d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Project
Overview
Use this skill to help a builder move from "the project is shippable" to "the project has launched in front of relevant audiences and has a follow-up loop." Optimize for borrowed relevance, not generic virality.
Run it as a co-creation, not a generation. Coach the best practices, recommend the platforms and posting times that fit the project, and interview the builder so the copy comes out in their voice. Do not fill placeholder templates and hand back paste-ready posts - that produces generic AI-slop copy. Draft from the builder's real material.
The primary audience is agentic builders and anyone shipping products with AI - indie SaaS, apps, AI products, AI agents, and developer tools - made by builders with small or nonexistent followings.
Source Of Truth
Read references/launch-workflow.md before doing launch work. It is the portable workflow shared by Codex, Claude Code, and other markdown-reading agents.
Read references/co-writing-guide.md when co-writing channel copy, outreach, replies, or recap text. It is an interview script and guardrails, not fill-in templates.
Read references/tone-guide.md alongside it before drafting or revising any public-facing copy. It sets the register, the tired-word bans, and how to build a tone profile from writing the builder has already done - including reference copy the builder pastes in so drafts match their real style.
Read references/scheduling.md when choosing which platforms fit the project and the optimal time to post to each.
Read references/video-production.md for an optional recipe when producing the launch video.
Read references/agent-recording.md when the builder opts in to the agent recording the launch video itself.
Operating Rules
- Co-create: interview the builder, draft from their own words and stories, and refine together. Never fill placeholder templates and hand back finished posts.
- If a draft would be generic because the builder's real input is missing, ask for it instead of inventing filler.
- Choose the two or three platforms that fit the project, and post at times optimized for the audience's timezone - not a generic every-channel blast.
- Prefer specific users, specific communities, and specific proof over broad "everyone should see this" distribution.
- Treat each platform as a community with norms, not a dumping ground for announcements.
- Never recommend upvote requests, vote manipulation, fake comments, engagement pods, undisclosed affiliation, sockpuppets, scraped cold spam, or rule-breaking self-promotion.
- Verify current official platform guidance before making real-launch channel claims.
- For Hacker News, distinguish Show HN from Launch HN. Most non-YC makers should use Show HN only when the product is tryable.
- For Product Hunt, focus on prepared assets, a useful first comment, feedback requests, and authentic engagement.
- For Reddit and private communities, check rules first and write as a participant, not an advertiser.
- For devtools, make installation, quickstart, docs, examples, licensing, release notes, and GitHub presentation part of launch readiness.
What ships with it
7 files 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.
- 6d ago First seen · 56 lines · 126 tokens per session scan A 0ed03dc982e3
launch-project is a skill published in the GitHub repository tonypls/agentic-product-launch (10 stars, last pushed 1mo ago), licensed MIT. It adds 126 tokens to every session and 926 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
magazine-web-ppt
For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.
submit-a-plugin
Submit a bb plugin to the BB Community marketplace. Use whenever a user asks to submit, list, publish, or add a plugin to the BB marketplace, or asks for a marketplace pull request. This skill validates the plugin and release, creates the marketplace entry, icon, screenshots, and long-form overview, and opens the pull…
workflows
Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.
memory
Use durable BB memory when prior project knowledge or cross-project user preferences can improve the current task, and save durable new learning through the bb memory CLI.
analyze-bundle
Convert Next.js bundle analyzer data to NDJSON and explore it.