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 apideck-libraries/api-skills --skill zendesk-sellgit clone --depth 1 https://github.com/apideck-libraries/api-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/apideck-libraries/api-skills/zendesk-sell)<a href="https://agentmods.dev/skills/apideck-libraries/api-skills/zendesk-sell"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/zendesk-sell/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/apideck-libraries/api-skills/zendesk-sell"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/zendesk-sell.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.00077 | $0.01871 |
| Opus 5.5 | $0.00031 | $0.00748 |
| Sonnet 5.5 | $0.00015 | $0.00374 |
| Haiku 4.5 | $0.00008 | $0.00187 |
Grade A, and why
zendesk-sell scanned grade A 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 15d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl 'https://unify.apideck.com/connector/connectors/zendesk-sell' \ How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zendesk Sell (via Apideck)
Access Zendesk Sell through Apideck's CRM unified API — one of 21 CRM connectors that share the same method surface. Code you write here ports to Odoo, Salesforce, HubSpot and 17 other CRM connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Zendesk Sell plumbing.
Quick facts
- Apideck serviceId:
zendesk-sell - Unified API: CRM
- Auth type: oauth2
- Gotchas: page
- Zendesk Sell docs: https://developer.zendesk.com/api-reference/sales-crm/
- Homepage: https://www.zendesk.com/sell/
At a glance
- Implementation difficulty: moderate — Self-Service OAuth App + No Confirmed Test Account
- Vendor partnership required: no
- Apideck-managed credentials: not available — The shared Apideck OAuth app for Zendesk Sell is deprecated.
- Account type required: Zendesk Sell account (the CRM product, not Zendesk Support).
- Consumer access level: A Sell user with the Agent or Admin role can authorize.
- Sandbox: not available — New Sell trials are not confirmed; testing needs an existing Zendesk Sell account.
- Rate limits: 36,000 requests per hour (10 per second), counted per token.
- Authentication: Authorization Code flow.
- Webhooks: No webhooks - changes are read by polling.
Important to know:
- Zendesk retires Zendesk Sell on 31 August 2027. Existing Sell accounts keep full access until then, so plan the integration around that end date; Zendesk has partnered with Pipedrive as the migration path.
Facts synced from Apideck's connector metadata API —
GET /connector/connectors/zendesk-sell(overviewfield) is the live, authoritative version.
When to use this skill
Activate this skill when the user explicitly wants to work with Zendesk Sell — for example, "pull contacts in Zendesk Sell" or "sync leads in Zendesk Sell". This skill teaches the agent:
What ships with it
1 file 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.
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.
- 15d ago Changed · +21 lines ad8b614aaab5
- 1mo ago First seen · 128 lines · 77 tokens per session scan A deba970d96dd
zendesk-sell is a skill published in the GitHub repository apideck-libraries/api-skills (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 1,871 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
component-family-consistency
Buttons, inputs, badges and pills share radius, colour logic, shadow, border and spacing. Use when building or reviewing a component library.
extract-design
Extract colours, typography, spacing, components and W3C design tokens from a live website with Dembrandt. Use when you need a site's real tokens or want to seed a design system from it.
modular-scale-typography
Ratio-based type scale where every size relates to the others. Use when defining font sizes or type tokens, or when typography feels arbitrary.
data-display-and-selection
View modes, row selection, mass actions, sorting, filters, search and table patterns. Use when designing data tables, listings, file browsers or any collection.
modal-and-overlay-patterns
Modals, drawers, bottom sheets and popovers, each with its scope and blocking level. Use when designing dialogs, confirmations, side panels or action sheets.
brand-visual-language
Shape language across type, radius and icons carries brand personality. Use when starting a design system, picking icons or radius tokens, or reviewing visual consistency.