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/agent-skills/installnpx skills add zapier/agent-skills --skill installgit clone --depth 1 https://github.com/zapier/agent-skillsWrote 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/agent-skills/install)<a href="https://agentmods.dev/skills/zapier/agent-skills/install"><img src="https://agentmods.dev/badge/skills/zapier/agent-skills/install.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.00055 | $0.03431 |
| Opus 5 | $0.00028 | $0.01716 |
| Sonnet 5 | $0.00011 | $0.00686 |
| Haiku 4.5 | $0.00006 | $0.00343 |
Grade B, and why
workflows-install scanned grade B with 1 finding 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
If global npm installs fail because of permissions, tell the user to fix their Node/npm setup before retrying. Prefer a user-owned Node install through nvm or Homebrew over `sudo npm install -g`. How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zapier Workflows Early Access Install
Imperative recipe. Each step gates the next. Do not skip a step that failed.
This is the public-first EA path. It uses the Zapier SDK CLI and does not install the legacy @zapier/zapier-sdk-code-substrate package.
Flow
flowchart TD
probe["1. Probe environment"] --> envOk{"Node 18+, npm, git OK?"}
envOk -->|no| stopEnv["STOP: tell user what to install"]
envOk -->|yes| installCli["2. Install or update SDK CLI"]
installCli --> verifyExperimental["3. Verify experimental commands"]
verifyExperimental --> commandsOk{"Code Workflows commands visible?"}
commandsOk -->|no| stopCli["STOP: diagnose SDK CLI install"]
commandsOk -->|yes| checkAuth["4. Check Zapier auth"]
checkAuth --> authOk{"JSON has data and no errors?"}
authOk -->|no| login["4b. Ask user to run interactive login"]
login --> checkAuth
authOk -->|yes| checkAccess["5. Check Zapier Workflows EA access"]
checkAccess --> accessOk{"Read-only workflow list succeeds?"}
accessOk -->|no| stopAccess["STOP: closed beta access required"]
accessOk -->|yes| installSkills["6. Bootstrap companion skills"]
installSkills --> report["7. Report success and next steps"]
What This Installs
@zapier/zapier-sdk-cli@latest— public npm package that provideszapier-sdk,zapier-sdk-cli, andzapier-sdk-experimental. Installed globally.- Five companion skills installed through the
skillsCLI:workflows/doctor,workflows/create,workflows/list,workflows/history, andworkflows/modify.
What this does not install:
@zapier/zapier-sdk-code-substrate— old private CLI path. Do not install it for EA.@zapier/zapier-durableglobally. The create skill installs or pins it inside workflow projects when needed.
Step 1: Probe Environment
Run each check. If any fails, stop and tell the user how to fix it.
node --version
npm --version
git --version
Expected output:
v18.0.0 # or higher
10.x.x # npm version; any current version is fine
git version 2.x.x
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.
- 5d ago First seen · 313 lines · 55 tokens per session scan B 87010f5583f2
workflows-install is a skill published in the GitHub repository zapier/agent-skills (17 stars, last pushed 11d ago), licensed MIT. It adds 55 tokens to every session and 3,431 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
testing-anti-patterns
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or…
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…
hypothesis-testing
Applies the scientific method to debugging by helping users form specific, testable hypotheses, design targeted experiments, and systematically confirm or reject theories to find root causes. Use when a user says their code isn't working, they're getting an error, something broke, they want to troubleshoot a bug, or…
trace-and-isolate
Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code. Use when a bug is hard to locate, code is not working as expected, an error or crash appears with unclear cause, a regression was introduced between recent commits, or you need to narrow down which component…
skill-authoring
Creates and structures SKILL.md files for AI coding agents, including YAML frontmatter, trigger phrases, directive instructions, decision trees, code examples, and verification checklists. Use when the user asks to write a new skill, create a skill file, author agent capabilities, generate skill documentation, or…