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 GTMify/aigtm --skill launchgit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/launch)<a href="https://agentmods.dev/skills/gtmify/aigtm/launch"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/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/gtmify/aigtm/launch"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01358 |
| Opus 5.5 | $0.00020 | $0.00543 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 139 lines · 51 tokens per session scan A bad83de9a94c
launch is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 12d ago), licensed MIT. It adds 51 tokens to every session and 1,358 once invoked, about $0.0002 per session on Opus 5.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
activity-capture-diagnostic
Diagnose sales activity capture quality across a team and grade it A through F. Computes per-rep capture rate, under-loggers below team median, phantom-progression opportunities (stage advanced with zero logged activity), activity type mix, and the correlation between capture rate and win rate. Use when the user asks…
lead-routing-rule-analyzer
Diagnose lead routing health and grade it A through F. Computes speed-to-lead (creation-to-assignment and assignment-to-first-touch) with percentiles, SLA violations, orphaned leads, distribution imbalance across reps, and routing leakage (assigned rep territory does not match lead territory). Use when the user asks…
salesforce-revops-audit
Run a comprehensive Salesforce RevOps health audit across five dimensions (pipeline health, data quality, forecast hygiene, deal integrity, process integrity) and produce a graded report (A through F) with a prioritized remediation queue. Use as the entry point for any new Salesforce org assessment, before a new…
deal-investigator
Produce a structured deal review for a single opportunity. Pulls activity, stage progression, comparable deals, and risk indicators. Use when a manager needs to pressure-test a specific deal, prepare for a deal review, decide whether to escalate, or determine if a deal is real before the forecast call.
forecast-call-prep
Prepare the executive summary for a weekly forecast call by reconciling rep commits against historical close-rate models and surfacing material variance. Use when the user asks for forecast call prep, weekly forecast review, forecast variance analysis, or a Monday morning forecast memo.
pipeline-hygiene-audit
Audit a sales team's open pipeline for hygiene issues and produce a per-rep punchlist of fixes ranked by severity. Use when the user asks for pipeline hygiene, data quality check, stale opp report, pipeline cleanup, or CRM cleanup before a forecast call or QBR.