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 skills add The-AI-Directory-Company/agents-and-skills --skill product-launch-briefgit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/skills/the-ai-directory-company/agents-and-skills/product-launch-brief)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/product-launch-brief"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/product-launch-brief/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/skills/the-ai-directory-company/agents-and-skills/product-launch-brief"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/product-launch-brief.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.00037 | $0.01528 |
| Opus 5 | $0.00018 | $0.00764 |
| Sonnet 5 | $0.00007 | $0.00306 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
product-launch-brief 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 9d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Launch Brief
Before you start
Gather the following from the user. Items 1-4 are required before proceeding:
- What is being launched? Feature, product, major update, or pricing change. Be specific about scope — "launching AI features" is too broad.
- Who is the target audience? Primary and secondary segments. Include their current behavior and what needs to change.
- Why should the audience care? The core value proposition in one sentence. If you cannot say it in one sentence, the positioning is not ready.
- When is the launch date? Fixed or flexible? Are there external dependencies (conference, partner launch, regulatory deadline)?
- What tier is this launch? Tier 1 (major — press, event, full campaign), Tier 2 (medium — blog, email, in-app), or Tier 3 (minor — changelog, docs update).
- What teams are involved? Product, engineering, marketing, sales, support, legal — who has a deliverable?
If the user says "we're launching next month, write the brief," push back: "What is the core value proposition, and who specifically is the target audience?"
Launch brief template
1. Launch Summary
- Product/Feature: [Name and one-line description]
- Launch Date: [Date, time, timezone]
- Launch Tier: [1 (major), 2 (medium), or 3 (minor)]
- Launch Owner: [Name and role]
- One-Line Pitch: [If a customer asks "what's new?" — this is the answer]
2. Positioning
Answer these three questions:
- For [target audience] who [current situation or pain point],
- this [product/feature] provides [key benefit],
- unlike [current alternative or competitor], it [key differentiator].
Write three versions: website, sales conversation, and internal alignment — same message at different detail levels.
3. Target Audience
| Segment | Description | Current Behavior | Desired Behavior | Key Message |
|---|---|---|---|---|
| Primary | [Who they are] | [What they do today] | [What you want them to do] | [Why they should switch] |
| Secondary | [Who they are] | [What they do today] | [What you want them to do] | [Why they should switch] |
What ships with it
3 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.
- 9d ago First seen · 133 lines · 37 tokens per session scan A 34d0ea10bf47
product-launch-brief is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,528 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.