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 tal7aouy/marketkit --skill market-launchgit clone --depth 1 https://github.com/tal7aouy/marketkitWrote 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/tal7aouy/marketkit/market-launch)<a href="https://agentmods.dev/skills/tal7aouy/marketkit/market-launch"><img src="https://agentmods.dev/badge/skills/tal7aouy/marketkit/market-launch/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/tal7aouy/marketkit/market-launch"><img src="https://agentmods.dev/badge/skills/tal7aouy/marketkit/market-launch.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.04167 |
| Opus 5 | $0.00000 | $0.02083 |
| Sonnet 5 | $0.00000 | $0.00833 |
| Haiku 4.5 | $0.00000 | $0.00417 |
Grade A, and why
market-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 8d 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.
This is a copy
100% identical to market-launch — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product/Service Launch Playbook Generator
Skill Purpose
Generate a complete, week-by-week launch playbook for any product, service, or feature launch. This skill produces a tactical plan with templates, checklists, email sequences, social posts, and metrics tracking -- everything needed to execute a successful launch.
When to Use
- User is planning to launch a new product, service, feature, or offering
- User asks for a launch plan, go-to-market strategy, or launch checklist
- User wants to coordinate a multi-channel launch campaign
- Triggered by
/market launchor/market launch <product description>
How to Execute
Step 1: Gather Launch Context
Before generating the playbook, collect these inputs from the user (ask if not provided):
- What are you launching? (product, service, feature, course, event)
- Who is the target audience? (demographics, pain points, existing list size)
- What is the primary launch goal? (revenue target, signups, downloads, awareness)
- What is the launch date? (or desired timeline)
- What channels do you have access to? (email list size, social following, ad budget, partnerships)
- What is the price point? (if applicable)
- Do you have existing customers/users? (for beta, testimonials, case studies)
- What is the budget? (bootstrapped, moderate, well-funded)
Step 2: Determine Launch Type
Select the primary launch strategy based on the user's context:
| Launch Type | Best For | Key Channel | Timeline |
|---|---|---|---|
| Product Hunt | SaaS, dev tools, consumer apps | Product Hunt + Twitter/X | 4-6 weeks prep |
| Email List Launch | Course, info product, SaaS with existing list | 6-8 weeks | |
| Social Media Launch | Consumer product, personal brand | Twitter/X, LinkedIn, Instagram | 4-6 weeks |
| Paid Ads Launch | E-commerce, established product | Facebook/Google Ads | 2-4 weeks prep |
| Community Launch | Niche product, developer tools | Reddit, Discord, Slack communities | 6-8 weeks |
| Partner Launch | B2B, enterprise, marketplace | Partner channels | 8-12 weeks |
| Hybrid Launch | Any high-stakes launch | Multi-channel coordinated | 8-12 weeks |
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.
- 8d ago First seen · 457 lines · 0 tokens per session scan A 0a7377592408
market-launch is a skill published in the GitHub repository tal7aouy/marketkit (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,167 tokens. A static security scan graded it A with 0 findings. It is 100% identical to market-launch, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
marketing-expert
Build comprehensive marketing technology solutions including automation workflows, campaign management, analytics tracking, and multi-channel orchestration. Use when the user mentions marketing automation, campaign management, SEO, email or content marketing, attribution, or multi-channel orchestration.
seo-technical
Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".
seo-sxo
Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says…
seo-flow
FLOW framework integration: evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO…
seo-page
Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says "analyze this page", "check page SEO", "single URL", "check this page", "page analysis", or provides a single URL for review.
seo-programmatic
Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when user says "programmatic SEO", "pages at scale", "dynamic pages", "template pages", "generated pages"…