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 cs-playbooksgit 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/cs-playbooks)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/cs-playbooks"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/cs-playbooks/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/cs-playbooks"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/cs-playbooks.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.00097 | $0.02008 |
| Opus 5 | $0.00048 | $0.01004 |
| Sonnet 5 | $0.00019 | $0.00402 |
| Haiku 4.5 | $0.00010 | $0.00201 |
Grade A, and why
cs-playbooks 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 5d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Success Playbooks
Overview
Customer Success is not reactive support — it is proactive value delivery that drives retention and expansion. This skill builds the CS operating system: Desired Outcome mapping (Lincoln Murphy), health scoring with leading indicators (Gainsight), CSQL identification for expansion, and playbooks per customer lifecycle stage.
When to Use
- "Build our customer success function"
- "Design customer onboarding"
- "Create a health score model"
- "Set up expansion plays"
- "Build QBR templates"
- "Customer comms during outage / incident"
- "CS crisis FAQ for support"
- "Retention crisis — churn wave response"
Authoritative Foundations
- Lincoln Murphy — Desired Outcome framework. Every customer has a Required Outcome and an Appropriate Experience. Success is their outcome, not your feature usage. The Success Gap: customers using the product correctly but still failing.
- Nick Mehta / Gainsight — CS ops at scale: health scores, lifecycle stages,
digital-first delivery. Operational layer on Murphy's strategy.
→
references/lincoln-murphy-customer-success.md - Allison Pickens — company-wide Customer Success. Treat retention and value delivery as a cross-functional operating model, not a CSM-only responsibility. Align post-sales roles around customer outcomes and use product signals to prioritize human intervention without confusing activity with value.
- Winning by Design SPICED — Post-sale lifecycle: onboarding → adoption → value realization → expansion → renewal.
Step-by-Step Process
Phase 1: Map the Customer Journey
Define stages: Onboarding → Activation (Day 1-7, aha moment) → Habit Formation (Week 2-6, usage signals) → Indispensability (Month 2-6, workflow integration) → Expansion → Renewal. Each stage has a milestone metric.
Phase 2: Build Health Scoring
Score 0-100: product usage (0-40), engagement depth (0-30), relationship health (0-30). Red (<50): immediate CSM outreach. Yellow (50-74): automated nurture. Green (75+): expansion targeting.
What ships with it
8 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/crisis-management-playbook.md 11 KB
- references/framework-notes.md 1.9 KB
- references/gtm-data-exchange-playbook.md 7.3 KB
- references/gtm-lifecycle-stages.md 8.6 KB
- references/lifecycle-metrics-by-stage.md 7.9 KB
- references/lincoln-murphy-customer-success.md 3.3 KB
- scripts/check-output.py 653 B runs code
- templates/output-template.md 806 B
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.
- 5d ago Changed · +5 lines 0d06cf932d18
- 10d ago First seen · 170 lines · 97 tokens per session scan A 7e6072c951aa
cs-playbooks is a skill published in the GitHub repository LeadMagic/gtm-skills (48 stars, last pushed 2d ago), licensed MIT. It adds 97 tokens to every session and 2,008 once invoked, about $0.0005 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.
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…
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…
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.