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 gtmagents/gtm-agents --skill expansion-playbookgit clone --depth 1 https://github.com/gtmagents/gtm-agentsWrote 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/gtmagents/gtm-agents/expansion-playbook)<a href="https://agentmods.dev/skills/gtmagents/gtm-agents/expansion-playbook"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/expansion-playbook/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/gtmagents/gtm-agents/expansion-playbook"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/expansion-playbook.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.00023 | $0.00277 |
| Opus 5 | $0.00012 | $0.00138 |
| Sonnet 5 | $0.00005 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
expansion-playbook 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- expansion-playbook — 100% identical, 0 lines differ
What it actually says
Expansion Playbook Library Skill
When to Use
- Preparing QBRs/EBRs where growth plays should be highlighted.
- Running account reviews to recommend upsell/cross-sell motions.
- Equipping AEs/CSMs with talk tracks and proof aligned to success milestones.
Framework
- Trigger Mapping – link product usage, milestone completion, or executive asks to specific plays.
- Value Narrative – outline business impact, ROI proof, and reference customers per play.
- Commercial Guardrails – specify packaging, pricing, approvals, and compensation cues.
- Enablement Kit – include decks, ROI calculators, success stories, and objection handling.
- Measurement – track attach rate, win rate, and cycle time for each play.
Templates
- Play card (trigger, narrative, assets, owners, KPIs).
- Executive talking points for expansion proposals.
- Post-play follow-up checklist with success metrics.
Tips
- Keep plays prioritized (top 3 per segment) to avoid overwhelm.
- Pair with
account-health-frameworkto time plays when risk is low. - Capture learnings after each motion to refine triggers + messaging.
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.
- 12d ago First seen · 32 lines · 23 tokens per session scan A 68af6e02e517
expansion-playbook is a skill published in the GitHub repository gtmagents/gtm-agents (399 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 277 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…