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 varunk130/ai-gtm-skill-library --skill launch-pulsegit clone --depth 1 https://github.com/varunk130/ai-gtm-skill-libraryWrote 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/varunk130/ai-gtm-skill-library/launch-pulse)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/launch-pulse"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/launch-pulse/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/varunk130/ai-gtm-skill-library/launch-pulse"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/launch-pulse.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.00049 | $0.02998 |
| Opus 5 | $0.00024 | $0.01499 |
| Sonnet 5 | $0.00010 | $0.00600 |
| Haiku 4.5 | $0.00005 | $0.00300 |
Grade A, and why
launch-pulse 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Pulse (VITAL Metrics Architecture)
A comprehensive measurement framework engine that designs the full analytics stack for tracking launch success -- from metric definitions through dashboard specifications to automated alert systems. VITAL ensures you measure what matters, detect problems early, and attribute results accurately across channels and touchpoints.
When to Use
- Designing the measurement framework for an upcoming launch
- Defining KPIs and success criteria for GTM initiatives
- Building dashboard specifications for different stakeholder audiences
- Setting up alert systems to detect launch issues early
- Choosing an attribution model for multi-channel campaigns
- Establishing baselines and targets before a launch
- Creating a metrics review cadence and reporting rhythm
What You'll Need
Critical inputs (ask if not provided):
- Product name and launch type (GA, beta, feature, expansion)
- Target audience and customer segments
- Business objectives and success criteria (revenue, adoption, pipeline targets)
- Marketing channels being activated (from demand-engine)
- Sales motion (PLG, sales-led, hybrid)
- Analytics tools and data infrastructure in use
Nice-to-have:
- Historical baselines for similar launches or products
- Current analytics setup and gaps
- Dashboard tools and BI platforms available
- Data team capacity and timeline
- Attribution tools currently deployed
- Customer journey maps (from journey-architect)
Process
Step 1: Build the VITAL Metrics Pyramid
The VITAL pyramid organizes metrics into five layers, each building on the one below. Start from the base (Volume) and work upward to Loyalty.
| Layer | Focus | Time Horizon | Audience | Signal Type |
|---|---|---|---|---|
| V - Volume | Reach and awareness | Daily | Marketing | Leading |
| I - Intent | Engagement and interest | Daily/Weekly | Marketing + Sales | Leading |
| T - Traction | Pipeline and conversion | Weekly | Sales + Revenue | Leading/Lagging |
| A - Adoption | Product usage and value | Weekly/Monthly | Product + CS | Lagging |
| L - Loyalty | Retention and advocacy | Monthly/Quarterly | CS + Executive | Lagging |
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 · 222 lines · 49 tokens per session scan A d4091d734bc9
launch-pulse is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (5 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 2,998 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-08-31.
Other skills, from other repositories
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…