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/connectors --skill perplexitygit clone --depth 1 https://github.com/zapier/connectorsWrote 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/connectors/perplexity)<a href="https://agentmods.dev/skills/zapier/connectors/perplexity"><img src="https://agentmods.dev/badge/skills/zapier/connectors/perplexity/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/connectors/perplexity"><img src="https://agentmods.dev/badge/skills/zapier/connectors/perplexity.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.00060 | $0.02204 |
| Opus 5.5 | $0.00024 | $0.00882 |
| Sonnet 5.5 | $0.00012 | $0.00441 |
| Haiku 4.5 | $0.00006 | $0.00220 |
Grade A, and why
perplexity 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 1mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
30 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.
- .claude-plugin/plugin.json 902 B
- .mcp.json 136 B
- CHANGELOG.md 123 B
- cli.js 7.3 KB runs code
- cli.ts 141 B runs code
- connections.ts 214 B runs code
- evals/evals.json 9.2 KB
- evals/results.md 1.8 KB
- index.ts 757 B runs code
- lib/perplexity.ts 3.9 KB runs code
- LICENSE 3.8 KB
- NOTICE 464 B
- package.json 1.5 KB
- README.md 8.5 KB
- references/perplexity-api-gotchas.md 7.1 KB
- references/use-as-cli.md 2.8 KB
- references/use-as-mcp.md 2.6 KB
- references/use-as-recipe.md 4.7 KB
- references/use-as-sdk.md 1.2 KB
- references/use-with-zapier.md 6.3 KB
- references/use-without-zapier.md 2.8 KB
- scripts/createAgent.ts 9.1 KB runs code
- scripts/getAgentResponse.ts 4.3 KB runs code
- scripts/listModels.ts 1.7 KB runs code
- scripts/search.ts 5.6 KB runs code
- tests/createAgent.test.ts 6.4 KB runs code
- tests/getAgentResponse.test.ts 2.7 KB runs code
- tests/listModels.test.ts 2.4 KB runs code
- tests/search.test.ts 3.9 KB runs code
- tsup.config.ts 1.9 KB runs code
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.
- 1mo ago First seen · 121 lines · 60 tokens per session scan A f962fc471ae1
perplexity is a skill published in the GitHub repository zapier/connectors (180 stars, last pushed 1mo ago), with no licence file. It adds 60 tokens to every session and 2,204 once invoked, about $0.0002 per session on Opus 5.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
basic-skill
Summarize small CSV files and identify the highest revenue month.
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…