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.
/plugin marketplace add zapier/agent-skillsnpx agentmods add plugins/zapier/agent-skills/agent-skillsgit 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/plugins/zapier/agent-skills/agent-skills)<a href="https://agentmods.dev/plugins/zapier/agent-skills/agent-skills"><img src="https://agentmods.dev/badge/plugins/zapier/agent-skills/agent-skills.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agent-skills 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
{
"name": "agent-skills",
"description": "Zapier agent skills for Claude Code. Built and maintained by Zapier teams.",
"version": "0.1.0",
"author": {
"name": "Zapier",
"email": "[email protected]",
"url": "https://zapier.com"
},
"homepage": "https://github.com/zapier/agent-skills",
"repository": "https://github.com/zapier/agent-skills",
"license": "MIT",
"keywords": [
"agent-skills",
"skills",
"zapier",
"workflows",
"automation",
"productivity"
],
"skills": [
"./skills/workflows/"
]
}
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 339 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 25 lines scan A ef0732a02648
agent-skills is a plugin published in the GitHub repository zapier/agent-skills (17 stars, last pushed 10d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
trackio-cli
Query Trackio projects, runs, and metrics using the trackio CLI. Use when the user needs to list projects/runs/metrics, get summaries, or retrieve metric values from local Trackio databases. Supports both human-readable and JSON output formats. Covers project discovery, run inspection, metric querying, and system met.
kage
Kage manages your memory and agents. It briefs and runs agents in isolated git worktrees for a single run or a multi-wave goal, re-runs the checks itself instead of trusting the agent's report, and remembers what it learns so each brief is smarter than the last.
collate
历史论文 OCR 校对工作流：PDF 预处理去水印去角标、MinerU OCR、三类文献（繁体古籍 / 民国排印 / 现代简体）校对、公众号排版导出.
mosaic-bridge
Mosaic Bridge — Unity MCP assistant agents for scene building, shader creation, and session continuity.
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
systematic-debugging
Diagnose root causes with a four-phase debugging protocol. Use for ANY technical issue — test failures, production bugs, unexpected behavior, performance problems, build failures, or integration issues. ESPECIALLY when under time pressure, when "one quick fix" seems obvious, or when previous fix attempts have failed.…