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/campaign-postmortemnpx skills add zapier/gtm-cheat-codes --skill campaign-postmortemgit 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/campaign-postmortem)<a href="https://agentmods.dev/skills/zapier/gtm-cheat-codes/campaign-postmortem"><img src="https://agentmods.dev/badge/skills/zapier/gtm-cheat-codes/campaign-postmortem.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 | $0.00027 | $0.00369 |
| Opus 5 | $0.00014 | $0.00185 |
| Sonnet 5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
campaign-postmortem 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 4d 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
Campaign Postmortem
Use When
A marketing team needs to understand what happened in a campaign and turn the learning into better next-cycle decisions.
Workflow
- Confirm campaign name, date range, goals, channels, and audience.
- Gather approved source material: brief, launch plan, project notes, performance data, meeting notes, and team feedback.
- Build a timeline of major decisions, launch events, results, and follow-up actions.
- Compare goals to actual results with source references.
- Separate observations from interpretations.
- Identify what worked, what did not work, root causes, and open questions.
- Recommend what to repeat, change, or stop.
- Add an action register with owners, dates, and unresolved decisions when available.
Zapier MCP And SDK Role
- Use Zapier MCP to gather approved campaign docs, conversations, dashboards, CRM context, meeting notes, and tracker state.
- Use Zapier SDK for retro intake, scheduled reminders, reviewer routing, action logging, and follow-up tracking.
- Keep metrics, claims, and broad sharing review-gated.
Output Format
- Executive summary
- Source list
- Campaign timeline
- Goal vs. actuals
- What worked
- What did not work
- Root causes and caveats
- Repeat / change / stop
- Action register
Guardrails
- Never invent metrics, attribution, causes, or owner commitments.
- Label missing data and conflicting evidence.
- Keep the retro focused on systems, decisions, and process, not personal blame.
- Require human review before sharing broadly or updating source-of-truth records.
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.
- 4d ago First seen · 47 lines · 27 tokens per session scan A 1f962515f7da
campaign-postmortem is a skill published in the GitHub repository zapier/gtm-cheat-codes (334 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 369 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.
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…
authorized-security-router
Route authorized defensive security and reverse-analysis tasks by scope, target type, user intent, and available toolchain before taking action. Use for APK review, static binary triage, frontend JavaScript security review, firmware inventory, malware/YARA analysis, API/LLM/supply-chain audit, security report…
git-native-context-contract
Create or review minimal Git-native project context using only adr, rfc, rule, spec, plan, rnd, and cpat documents; human-gated draft/accepted/rejected lifecycle; implements, dependson, extends, and related relations; and evidence-backed code-change patterns. Use when a project needs durable decisions, specifications…