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 agentmods add skills/anthropics/knowledge-work-plugins/ticket-triagenpx skills add anthropics/knowledge-work-plugins --skill ticket-triagegit clone --depth 1 https://github.com/anthropics/knowledge-work-pluginsWrote 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/anthropics/knowledge-work-plugins/ticket-triage)<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/ticket-triage"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/ticket-triage.svg" alt="Measured on agentmods" 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 | $0.00054 | $0.02447 |
| Opus 5 | $0.00027 | $0.01223 |
| Sonnet 5 | $0.00011 | $0.00489 |
| Haiku 4.5 | $0.00005 | $0.00245 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ticket-triage
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Categorize, prioritize, and route an incoming support ticket or customer issue. Produces a structured triage assessment with a suggested initial response.
Usage
/ticket-triage <ticket text, customer message, or issue description>
Examples:
/ticket-triage Customer says their dashboard has been showing a blank page since this morning/ticket-triage "I was charged twice for my subscription this month"/ticket-triage User can't connect their SSO — getting a 403 error on the callback URL/ticket-triage Feature request: they want to export reports as PDF
Workflow
1. Parse the Issue
Read the input and extract:
- Core problem: What is the customer actually experiencing?
- Symptoms: What specific behavior or error are they seeing?
- Customer context: Who is this? Any account details, plan level, or history available?
- Urgency signals: Are they blocked? Is this production? How many users affected?
- Emotional state: Frustrated, confused, matter-of-fact, escalating?
2. Categorize and Prioritize
Using the category taxonomy and priority framework below:
- Assign a primary category (bug, how-to, feature request, billing, account, integration, security, data, performance) and an optional secondary category
- Assign a priority (P1–P4) based on impact and urgency
- Identify the product area the issue maps to
3. Check for Duplicates and Known Issues
Before routing, check available sources:
- ~~support platform: Search for similar open or recently resolved tickets
- ~~knowledge base: Check for known issues or existing documentation
- ~~project tracker: Check if there's an existing bug report or feature request
Apply the duplicate detection process below.
4. Determine Routing
Using the routing rules below, recommend which team or queue should handle this based on category and complexity.
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 · 276 lines · 54 tokens per session scan A d0e5e95443e3
ticket-triage is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,839 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 2,447 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…