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 agentmods add skills/zapier/gtm-cheat-codes/customer-deck-buildernpx skills add zapier/gtm-cheat-codes --skill customer-deck-buildergit clone --depth 1 https://github.com/zapier/gtm-cheat-codesWrote 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/zapier/gtm-cheat-codes/customer-deck-builder)<a href="https://agentmods.dev/skills/zapier/gtm-cheat-codes/customer-deck-builder"><img src="https://agentmods.dev/badge/skills/zapier/gtm-cheat-codes/customer-deck-builder.svg" alt="Measured on agentmods" 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.00029 | $0.01013 |
| Opus 5 | $0.00015 | $0.00507 |
| Sonnet 5 | $0.00006 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
customer-deck-builder 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Deck Builder
Use this skill when a GTM team needs a customer-facing deck for discovery, QBR, renewal, expansion, executive briefing, onboarding, or follow-up.
Workflow
- Gather the minimum context:
- company name, domain, or account ID
- call type
- meeting goal
- attendee roles
- specific topics, questions, or risks
- Resolve the account from approved CRM or account-data sources.
- Pull only the approved fields needed for the deck:
- account plan and renewal context
- usage summary
- active users or builder roles
- top apps and workflows
- feature adoption
- relevant customer notes or meeting context
- Choose the right deck shape:
- discovery or first meeting
- QBR or business review
- renewal
- expansion or upsell
- executive briefing
- onboarding kickoff
- follow-up or check-in
- Build the narrative before writing slides:
- what the customer is doing today
- what value they are already getting
- what risks, gaps, or opportunities are visible
- which use cases fit their stack, role, or goal
- what next step should come out of the meeting
- Write slide-by-slide markdown for Gamma.
- Generate the deck through Zapier MCP using Gamma actions.
- Return the Gamma URL, deck summary, and review notes.
Deck Structures
Discovery Or First Meeting
Goal: establish credibility, show useful context, and frame relevant automation opportunities.
Suggested slides:
- Cover
- Agenda
- What we know about the customer
- AI automation opportunity
- Where to start
- Relevant use cases
- Customer proof
- Next steps
QBR Or Business Review
Goal: show value delivered, identify optimization opportunities, and align on next steps.
Suggested slides:
- Cover
- Agenda
- Customer and Zapier team
- Account health overview
- Usage trend or task-limit utilization
- Feature adoption
- Top workflows and apps
- Opportunities
- Progress and next steps
Renewal
Goal: recap value, show trajectory, and connect the renewal conversation to measurable outcomes.
What ships with it
5 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.
- 6d ago First seen · 163 lines · 29 tokens per session scan A 1013496ba6c3
customer-deck-builder is a skill published in the GitHub repository zapier/gtm-cheat-codes (334 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 1,013 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
weave
Parallel strand orchestration — decompose a task into 3+ independently scoped strands, fan out real subagents (worktree-isolated when they write files), and coordinate through a session file and Insight Capsules. Use ONLY when the user explicitly invokes it by name or slash command.
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
premortem
First-principles premortem on a high-stakes plan: assume failure 6–18 months out, reconstruct causal death chains, surface hidden assumptions, deliver a revised reversibility-weighted plan. Use ONLY when the user explicitly invokes it by name or slash command.
bcc-plan-spar
BCC align+lock+review PLAN.md for one slice (no product code). Slash: /bcc-plan-spar · chat: bcc:plan-spar · "lock PLAN" · spar the plan. Args: rounds=N (auto-review cap), review=self|subagent|cli|auto|off. Grill until clear enough (no default Q&A quota). Hand off to bcc-clean-cut after human APPROVE.
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.
anti-slop-review
Review an implemented product UI or public prose surface for hard visual defects, design-system incoherence, repeated template patterns, and AI-writing tells without treating subjective taste as universal law. Use for pre-ship screenshots, browser review, README/tool-page copy, launch notes, guide prose, or redesigns…