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/gtm-cheat-codes --skill support-ticket-triagegit clone --depth 1 https://github.com/zapier/gtm-cheat-codesWrote 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/gtm-cheat-codes/support-ticket-triage)<a href="https://agentmods.dev/skills/zapier/gtm-cheat-codes/support-ticket-triage"><img src="https://agentmods.dev/badge/skills/zapier/gtm-cheat-codes/support-ticket-triage/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/gtm-cheat-codes/support-ticket-triage"><img src="https://agentmods.dev/badge/skills/zapier/gtm-cheat-codes/support-ticket-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.00547 |
| Opus 5 | $0.00019 | $0.00273 |
| Sonnet 5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
support-ticket-triage 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 9d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Support Ticket Triage Agent
Use this skill when a support rep needs fast, source-backed context before replying to a customer ticket.
Workflow
- Accept a ticket URL, ticket ID, or pasted customer message.
- Pull ticket context through Zapier MCP: subject, body, comments, requester, tags, priority, custom fields, status, and assignee.
- Search connected systems in parallel:
- Defect tracker for open or recently fixed bugs.
- Feature backlog for known gaps or expected behavior.
- Helpdesk history for similar tickets and resolutions.
- Knowledge base for docs, runbooks, and troubleshooting steps.
- Classify the issue into exactly one category: known defect, feature gap, configuration issue, performance issue, or novel issue.
- Return a concise triage summary with evidence, relevant links, and a recommended next action.
- Draft a customer-facing reply only when the rep asks.
Zapier MCP And SDK Role
- Use Zapier MCP to read helpdesk tickets, comments, requester details, issue tracker records, feature backlog items, knowledge-base docs, and optional CRM or account context.
- Use Zapier SDK only if the workflow becomes a durable automation, such as tagging, escalation packet creation, similar-ticket linking, SLA warnings, follow-up reminders, regression alerts, or triage digests.
- Keep customer replies, ticket updates, tags, escalation packets, and broad alerts human-approved.
Output Format
- Ticket category
- Best matching evidence
- Related docs or similar tickets
- Recommended next action
- Optional customer reply draft
- Open questions or escalation gaps
Guardrails
- Do not auto-reply to customers.
- Do not expose internal defect IDs, sprint numbers, or engineering-only notes in customer-facing drafts.
- Do not query observability tools unless the rep provides a concrete signal such as a trace ID, timestamp, error code, or request ID.
- Do not invent matches, timelines, fixes, or customer-impact claims.
- Do not store ticket data beyond the working session unless the approved workflow explicitly requires it.
What ships with it
5 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.
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.
- 9d ago First seen · 49 lines · 38 tokens per session scan A 2eef939125cd
support-ticket-triage is a skill published in the GitHub repository zapier/gtm-cheat-codes (334 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 547 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
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-bug-readiness
Use when assessing a Jira bug ticket for AI autofix readiness. Produces a structured JSON verdict (ready/needsinfo/notfixable) based on a three-gate rubric. Designed for CI pipeline use with the jira-triage orchestrator.
ai-bug-fix-triage
Triage JIRA bugs against repository code to classify AI fixability. Use when reviewing a backlog of bugs to determine which ones an AI agent can fix.
code-context
How to answer codebase questions with the code-context MCP tools (search, sql, reindex): ranked hybrid keyword+semantic search, relevance-ranked SQL aggregation over the index, and index lifecycle. Use when a question spans many files ("how does X work", "where is Y handled"), when ranking or counting code by topic…
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.
bugpack-list-bugs
List all tracked bugs from BugPack with status and project filtering. Use when: user asks about bugs, pending issues, bug lists, or wants to see what needs fixing. NOT for: viewing detailed bug context (use bugpack-view-bug) or fixing bugs (use bugpack-fix-bug).