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/gtmify/aigtm/launchnpx skills add GTMify/aigtm --skill launchgit clone --depth 1 https://github.com/GTMify/aigtmWhat 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.00051 | $0.01358 |
| Opus 5 | $0.00026 | $0.00679 |
| Sonnet 5 | $0.00010 | $0.00272 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
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 2d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Planner
Your Role
You are a senior product marketing lead running a coordinated launch. Your job is to translate "we built this" into a multi-week, multi-channel, multi-audience plan with every asset spec'd out — not a 200-bullet checklist but a tight plan a small team can actually execute.
Process
Step 1: Define the Launch
Collect:
- What's launching: Product, feature, integration, repackaging, expansion
- Audience: Existing customers / prospects / both — and which segment(s)
- The one sentence: If a customer reads only the headline, what should they take away?
- The proof: Why now, why this, why us — with evidence
- Constraints: Date, team capacity, budget, channels available
Step 2: Tier the Launch
Match scale to investment. Three tiers:
| Tier | When | Investment |
|---|---|---|
| Tier 1 — Hero | Major new product, repositioning | 6-8 weeks lead time, full stack, paid included |
| Tier 2 — Feature | Significant new capability | 3-4 weeks lead time, organic + email |
| Tier 3 — Update | Incremental improvement | 1 week, changelog + customer email |
Pick the tier honestly. Over-investing in a Tier 3 wastes capacity; under-investing in a Tier 1 wastes the opportunity.
Step 3: Build the Audience Matrix
For each audience, define:
- The pain this launch addresses
- The before/after state
- The proof point most relevant to them
- The CTA
A B2B launch usually hits at least: existing customers, active prospects, cold market, and internal team.
Step 4: Write the Messaging Hierarchy
Three layers:
- One sentence (used in headlines, social, sales scripts)
- One paragraph (used in landing page hero, email body, deck slide)
- The full story (used in blog post, talk track, FAQ)
All three must say the same thing, just at different fidelity. Inconsistency across layers kills credibility.
Step 5: Spec the Content Kit
Tier 1 launch kit:
- Landing page or microsite
- Launch blog post (~800-1200 words)
- Customer announcement email
- Prospect announcement email
- 3-5 LinkedIn posts (founder, exec, PMM, sales)
- 1 X/Twitter thread
- 1 demo video script (60-90 sec)
- 1 webinar deck (if Tier 1)
- Sales enablement: 1-pager, talk track, FAQ, objection handling
- Press: pitch + customer quote (only if newsworthy)
- Optional: launch partner co-marketing, analyst briefing brief
What ships with it
2 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.
- 2d ago First seen · 139 lines · 51 tokens per session scan A bad83de9a94c
launch is a skill published in the GitHub repository GTMify/aigtm (24 stars, last pushed 24d ago), licensed MIT. It adds 51 tokens to every session and 1,358 once invoked, about $0.0003 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-30.
Other skills, from other repositories
gh-issue-to-demand-signal
Takes a competitor's public GitHub repo URL, fetches their open issues via the GitHub REST API, filters noise locally, clusters issues into 6 demand categories, computes a demand score per issue and per cluster, and outputs a ranked demand gap report with a GTM messaging brief. Use when asked to scan a competitor's…
graphic-ebook
Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF. 3–10 pages, 9 style presets, 11 page layout types. Trigger when user says "create an ebook", "design a lead magnet", "make a PDF guide", "build a gated content piece", "write a B2B ebook", "design a white paper", "create a…
map-your-market
Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences, then synthesizes everything into a positioning framework showing who your ICP is, what they say out loud, and exactly how…
company-radar
Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.
dependency-update-bot
Scans your project for outdated npm, pip, Cargo, Go, or Ruby packages. Runs a CVE security audit. Fetches changelogs, summarizes breaking changes with Gemini, and opens one PR per risk group (patch, minor, major). Includes Diagnosis Mode for install conflicts. Use when asked to update dependencies, check for outdated…
producthunt-launch-kit
Use when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets. Generates tagline variants under 60 chars, a 500-char description, a maker comment, launch-day tweet thread, LinkedIn post, and a 4-email launch sequence.