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/sales-sequence-buildernpx skills add zapier/gtm-cheat-codes --skill sales-sequence-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/sales-sequence-builder)<a href="https://agentmods.dev/skills/zapier/gtm-cheat-codes/sales-sequence-builder"><img src="https://agentmods.dev/badge/skills/zapier/gtm-cheat-codes/sales-sequence-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.00020 | $0.00235 |
| Opus 5 | $0.00010 | $0.00118 |
| Sonnet 5 | $0.00004 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
sales-sequence-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.
What it actually says
Sales Sequence Builder
Use this skill when a GTM team needs rep-ready sequence copy for outbound, event follow-up, re-engagement, or signal-based outreach.
Workflow
- Gather the minimum context needed to make the sequence specific.
- Separate reusable elements from reference copy from elements that must change for this audience.
- Draft concise steps with clear CTAs and plainspoken language.
- Add operator notes for personalization, claims, and routing.
- Keep sensitive signals useful without sounding invasive.
Zapier MCP And SDK Role
- Use Zapier MCP to read CRM, approved campaign docs, account notes, and message context.
- Use Zapier SDK for sequence request intake, task creation, and approved draft logging when the workflow repeats.
- Keep Gmail drafts, CRM tasks, sequence enrollment, and sends rep-approved.
Guardrails
- Do not blindly port copy from another campaign.
- Do not imply unsupported claims, custom audits, or executive involvement.
- Do not create Gmail or CRM drafts without approval.
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 · 29 lines · 20 tokens per session scan A abda98be6584
sales-sequence-builder is a skill published in the GitHub repository zapier/gtm-cheat-codes (334 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 235 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…