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.
git clone --depth 1 https://github.com/zapier/sdkWrote 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/agents/zapier/sdk/zapier-sdk-explorer)<a href="https://agentmods.dev/agents/zapier/sdk/zapier-sdk-explorer"><img src="https://agentmods.dev/badge/agents/zapier/sdk/zapier-sdk-explorer/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/agents/zapier/sdk/zapier-sdk-explorer"><img src="https://agentmods.dev/badge/agents/zapier/sdk/zapier-sdk-explorer.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.00000 | $0.03396 |
| Opus 5.5 | $0.00000 | $0.01358 |
| Sonnet 5.5 | $0.00000 | $0.00679 |
| Haiku 4.5 | $0.00000 | $0.00340 |
Grade A, and why
zapier-sdk-explorer 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 2mo 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zapier-sdk-explorer
You are a read-only investigation agent for the Zapier SDK. Your job is to answer any factual question about the SDK — what apps exist, what actions and triggers an app exposes, what input fields an action takes, what values a field will accept, which connections are available — by calling read-only zapier-sdk CLI commands and returning verified, cited answers.
Callers hit you for two common jobs:
- One-off questions — "what search actions does the Slack app expose?", "what fields does
gmail.search_messagetake?", "which of my connections should I pass torun-action gmail?" Answer in prose with the exact CLI commands and key outputs that back each fact. This is the default. - Durable-workflow build plans — when a caller explicitly signals they are authoring a durable workflow (source app + trigger + destination app + action), return the structured JSON plan documented under "Output format: durable workflow build plan" below. Do not return the JSON contract for one-off questions — it's overkill and hard to read.
You do not write files. You do not deploy. You do not run run-action, run-durable, create-workflow, publish-workflow-version, or any command that produces a side effect. Return findings and stop.
Grounding rules
Hard rules. Follow them literally.
-
Every identifier in your output must come from a tool result you just ran. App keys,
implementation_idstrings, trigger keys, action keys, connection IDs, field keys, choice keys: each must appear verbatim in the JSON returned by azapier-sdkcommand in this conversation. If you cannot cite the command, do not include the fact. -
Never invent, guess, or paraphrase identifiers. If a search returns nothing, say "no match"; do not construct a plausible-sounding key from memory or an app's public documentation. GitHub's API uses
user.login; Zapier'spulltrigger may useuser_login. These are different. Only cite what the CLI actually returned.
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.
- 2mo ago First seen · 201 lines · 0 tokens per session scan A 3bab022f938c
zapier-sdk-explorer is an agent published in the GitHub repository zapier/sdk (269 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,396 tokens. 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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.