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 zapier/zapier-mcp --skill zapier-exploregit clone --depth 1 https://github.com/zapier/zapier-mcpWrote 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/zapier-mcp/zapier-explore)<a href="https://agentmods.dev/skills/zapier/zapier-mcp/zapier-explore"><img src="https://agentmods.dev/badge/skills/zapier/zapier-mcp/zapier-explore/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/zapier/zapier-mcp/zapier-explore"><img src="https://agentmods.dev/badge/skills/zapier/zapier-mcp/zapier-explore.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.00130 | $0.03742 |
| Opus 5 | $0.00065 | $0.01871 |
| Sonnet 5 | $0.00026 | $0.00748 |
| Haiku 4.5 | $0.00013 | $0.00374 |
Grade A, and why
zapier-explore 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 11d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zapier explore
Help the user expand beyond the first action — figure out what Zapier MCP can do for them based on their role and apps, then walk them through enabling a starter set of actions tailored to that work.
This is the natural follow-on to zapier-demo. Demo proves one action works; explore turns that into a real toolkit for the user's day-to-day.
For how the Zapier MCP server itself works, see docs.zapier.com/mcp.
When to use vs. other skills
- zapier-explore (this skill) — role-tailored expansion. Interview + use cases + configuration.
- zapier-demo — one app, one action, run it live. Run this first if the user hasn't seen Zapier work yet.
- zapier-onboard — pitch + connect. Server-level authentication only. Run this before demo if the server isn't connected.
- zapier-status — health checks and audits on an existing setup.
If the user hasn't run their first action yet, route to zapier-demo first — explore works best after a win.
Step 1: Interview
Keep it short — two or three questions, not a survey. Adapt follow-ups based on answers.
Open with:
"Let's figure out what to add to your Zapier toolkit. Quick context first — what do you do for work, and what apps are you in every day?"
Listen for:
- Role / function (engineer, PM, sales, marketing, founder, support, creator, ops, recruiter, finance, exec, personal)
- Named apps (Slack, Gmail, Jira, HubSpot, etc.)
- Industry signals (sole automation builder vs. on a team, B2B vs. consumer, startup vs. enterprise)
If they give you only role or only apps, ask one follow-up. If they give you both, optionally ask:
"Is there a task you keep redoing manually that you'd love to delegate?"
Don't push past three questions. Move on with what you've got.
Step 2: Suggest use cases
Pick the role library below that best matches the user's answers (multiple is fine — combine for hybrid roles). For each, surface 4–6 use cases tailored to the apps they mentioned. If they named an app you don't have in the library, default to the closest equivalent (e.g., "Outlook" → use the Gmail patterns; "Monday.com" → use the Asana patterns).
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.
- 11d ago First seen · 248 lines · 130 tokens per session scan A f047ce82ae5b
zapier-explore is a skill published in the GitHub repository zapier/zapier-mcp (405 stars, last pushed 1mo ago), licensed MIT. It adds 130 tokens to every session and 3,742 once invoked, about $0.0006 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
token-efficiency
Token conservation economics, bounded context-window pruning, AST structural query optimization, and high-precision prompt budget discipline.
houseclean
Cross-drive storage audit and cleanup. Surveys all drives, finds orphaned git worktrees, large AI tool caches (.ollama, .gemini, .cursor, npm, pip), and buildable artifacts (nodemodules, .venv). Produces a prioritized action plan with specific migration commands. Use when disk space is low or worktrees need cleanup…
schedule
Manages recurring and one-off scheduled tasks. Session-scoped scheduling via CronCreate/CronDelete/CronList. Documents the cloud path for tasks that need to survive machine sleep or network drops.
mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
phx-mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
quick
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.