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 LeadMagic/gtm-skills --skill gtm-metricsgit clone --depth 1 https://github.com/LeadMagic/gtm-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/leadmagic/gtm-skills/gtm-metrics)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/gtm-metrics"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/gtm-metrics/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/leadmagic/gtm-skills/gtm-metrics"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/gtm-metrics.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.00062 | $0.07155 |
| Opus 5 | $0.00031 | $0.03578 |
| Sonnet 5 | $0.00012 | $0.01431 |
| Haiku 4.5 | $0.00006 | $0.00715 |
Grade A, and why
gtm-metrics 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 6d 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 — 473 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM Metrics
Overview
GTM Metrics establishes the canonical measurement framework for evaluating go-to-market health. The core principle: most SaaS companies measure the wrong things or measure the right things incorrectly. They track MRR without segmenting by cohort, calculate CAC without fully loading costs, and report NRR without distinguishing expansion from contraction. This skill prevents the existential mistake of running a GTM organization on bad math.
The non-obvious rule: every SaaS metric is stage-dependent. A 3-month CAC payback is spectacular at the enterprise level and mediocre in SMB. A 90% NRR is catastrophic for enterprise SaaS and acceptable for SMB. Benchmarks are meaningless without stage context. This skill applies stage-aware benchmarking to every metric.
This skill produces a complete GTM Metrics Dashboard including: the 6-metric core stack with stage-aware benchmarks, a Winning by Design GTM Index assessment scoring the organization 1-10 across 6 models, pipeline velocity analysis with bottleneck identification, cohort trend charts, and a board-ready executive summary with red/yellow/green status indicators.
When to Use
- User says "GTM metrics" or "SaaS metrics dashboard" → activate this skill
- User asks "how efficient is our GTM" or "GTM efficiency" → use this skill
- User mentions "board metrics," "board deck," or "investor reporting" → activate for metric preparation
- User says "pipeline velocity," "CAC payback," "Magic Number," or "Rule of 40" → specific metric analysis
- User asks "how do we compare" or "benchmarks for our stage" → apply stage-aware benchmarks
- User mentions "Winning by Design" or "GTM Index" → score the organization
- Trigger phrases: SaaS metrics, pipeline metrics, NRR, LTV:CAC, unit economics, GTM efficiency, revenue efficiency, growth efficiency
Do NOT use for:
- Campaign-specific analytics (open rates, reply rates, meeting rates) → use campaign-analytics
- Pipeline management and hygiene (CRM data quality, stage definitions) → use pipeline-management
- Detailed calculator with interactive inputs → use saas-metrics-calculator
- Multi-touch marketing attribution → use attribution
- Deal-specific pricing and proposals → use deal-desk
What ships with it
18 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.
- references/activation-playbook.md 6.9 KB
- references/b2b-influencer-measurement.md 6.6 KB
- references/benchmark-reconciliation.md 24 KB
- references/bookings-billings-revenue-matrix.md 5.4 KB
- references/chris-walker-mental-models.md 5.2 KB
- references/dharmesh-shah-hubspot-inbound.md 7.9 KB
- references/force-management-playbook.md 6.6 KB
- references/framework-notes.md 949 B
- references/gtm-lifecycle-stages.md 8.6 KB
- references/gtm-metrics-scorecard.md 1.1 KB
- references/lifecycle-metrics-by-stage.md 7.9 KB
- references/meritech-saas-benchmarks.md 7.5 KB
- references/public-company-gtm-metrics.md 6.1 KB
- references/saas-mrr-accounting-nuances.md 9.6 KB
- scripts/check-output.py 652 B runs code
- templates/lifecycle-monitoring-dashboard.md 3.6 KB
- templates/output-template.md 1.5 KB
- templates/stage-health-scorecard.md 4.8 KB
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.
- 6d ago Changed 6c8adfc9cc08
- 10d ago First seen · 473 lines · 62 tokens per session scan A 52b5b8ccf8ca
gtm-metrics is a skill published in the GitHub repository LeadMagic/gtm-skills (48 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 7,155 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
startup-launch-playbook
A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.
competitor-monitoring
Use this skill when you need to know what rival companies are doing — "what are my competitors doing", "competitor update", "competitor news", "competitive landscape", "market intel", "what's new with [company]", "track [company]", "competitor briefing", "who's making moves", "we keep losing deals to [company]" — or…
multichannel-campaign-builder
Use this skill when someone needs a complete outbound sequence written — every touch across LinkedIn and email, not a single cold email. Produces three distinct angles to choose from, then the full sequence with each message ready to send, calibrated to the campaign type and channel mix and self-checked against a…
cialdini-influence
Applies Cialdini's seven principles of ethical persuasion -- Reciprocity, Commitment and Consistency, Social Proof, Authority, Liking, Scarcity, and Unity -- to business contexts including sales, marketing, fundraising, and negotiation. Use when designing conversion funnels, optimizing sales processes, preparing…
inbox-digest
Scan the last 48 hours of unread newsletters, news emails, and blog digests. Summarize what's relevant to your work. Trigger when the user asks "what did I miss", "any interesting newsletters", or as part of the morning briefing ritual.
meeting-prep
Build a pre-meeting briefing — who's in the room, what they care about, your goal, and the questions to ask. Trigger when the user asks to prep for a meeting or call, "what should I know before", or names an upcoming meeting.