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 iblai/enterprise-agents --skill zendeskgit clone --depth 1 https://github.com/iblai/enterprise-agentsWrote 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/iblai/enterprise-agents/zendesk)<a href="https://agentmods.dev/skills/iblai/enterprise-agents/zendesk"><img src="https://agentmods.dev/badge/skills/iblai/enterprise-agents/zendesk/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/iblai/enterprise-agents/zendesk"><img src="https://agentmods.dev/badge/skills/iblai/enterprise-agents/zendesk.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.00037 | $0.00606 |
| Opus 5 | $0.00018 | $0.00303 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
zendesk 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 10d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zendesk
What it is
Zendesk is a widely used customer service and ticketing platform, serving as the primary helpdesk for customer-facing support teams in this segment. The customer support agent uses Zendesk to open and update tickets on behalf of customers, retrieve account and organization context tied to a requester, apply canned response macros, and monitor SLA compliance. It is also used to fetch CSAT scores and tag tickets for quality analysis.
When to use this skill
- Creating a new support ticket from a customer inquiry
- Updating ticket status, priority, or assignee during an escalation
- Searching for existing tickets from a customer to understand their issue history
- Applying a macro (canned response template) to a ticket
- Retrieving CSAT rating and comments for a resolved ticket
- Looking up a customer's organization record for account context
Credentials
This skill authenticates using variables from ~/.openclaw/.env (template: .env.example at the config root). Required variables:
ZENDESK_SUBDOMAIN- Zendesk subdomain (e.g.mycompanyformycompany.zendesk.com)ZENDESK_EMAIL- email of the agent/service account performing API callsZENDESK_API_TOKEN- API token from the Zendesk Admin Center
Key operations
GET /api/v2/tickets/{ticket_id}- retrieve a ticket by IDPOST /api/v2/tickets- create a new ticketPUT /api/v2/tickets/{ticket_id}- update ticket fieldsGET /api/v2/search?query=...- full-text search across tickets, users, and orgsPOST /api/v2/tickets/{ticket_id}/macros/apply/{macro_id}- apply a macro to a ticketGET /api/v2/users/{user_id}- retrieve a user (requester) profile
Notes
- Authenticate with
{email}/token:{api_token}using HTTP Basic. - Rate limit is 700 requests/minute across all endpoints for Enterprise plans; lower tiers have stricter limits.
- Ticket side-loads (e.g.,
?include=users,organizations) reduce round-trips but count as additional data points toward rate limits. - Sandbox Zendesk instances have separate subdomains; never write test tickets to production.
- Attachments in tickets are retrieved via pre-signed URLs and expire after 24 hours.
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.
- 10d ago First seen · 40 lines · 37 tokens per session scan A d1c22a0b6111
zendesk is a skill published in the GitHub repository iblai/enterprise-agents (11 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 606 once invoked, about $0.0002 per session on Opus 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
innovaccer
Innovaccer — lets an agent query population health analytics, patient risk scores, care gap lists, and SDOH screening data from the Innovaccer unified patient data platform.
availity
Availity Essentials — lets an agent perform real-time eligibility verification, prior authorization initiation and status checks, and payer enrollment management via the Availity clearinghouse REST API.
cerner-fhir
Cerner Millennium FHIR R4 API — lets an agent read patient clinical data (demographics, encounters, diagnoses, medications, notes) within a Cerner-hosted health system.
epic-fhir
Epic EHR FHIR R4 API — lets an agent read and write patient clinical data (demographics, encounters, diagnoses, medications, notes, orders) within an Epic-hosted health system.
healthstream
HealthStream LMS — lets an agent query employee training transcripts, assign compliance curricula, check credential expiration alerts, and pull completion reports from the HealthStream learning management system.
micromedex
Micromedex (Merative/IBM) — lets an agent perform drug interaction screening, dose range checking, toxicology lookups, and IV compatibility queries using the Micromedex drug knowledge base.