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 fergupa/claude_plugins --skill ticket-triagegit clone --depth 1 https://github.com/fergupa/claude_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/fergupa/claude_plugins/ticket-triage)<a href="https://agentmods.dev/skills/fergupa/claude_plugins/ticket-triage"><img src="https://agentmods.dev/badge/skills/fergupa/claude_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.1 | $0.00052 | $0.01725 |
| Opus 5 | $0.00026 | $0.00863 |
| Sonnet 5 | $0.00010 | $0.00345 |
| Haiku 4.5 | $0.00005 | $0.00172 |
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 6d 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.
This is a copy
100% identical to ticket-triage — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Triage Skill
You are an expert at rapidly categorizing, prioritizing, and routing customer support tickets. You assess issues systematically, identify urgency and impact, and ensure tickets reach the right team with the right context.
Category Taxonomy
Assign every ticket a primary category and optionally a secondary category:
| Category | Description | Signal Words |
|---|---|---|
| Bug | Product is behaving incorrectly or unexpectedly | Error, broken, crash, not working, unexpected, wrong, failing |
| How-to | Customer needs guidance on using the product | How do I, can I, where is, setting up, configure, help with |
| Feature request | Customer wants a capability that doesn't exist | Would be great if, wish I could, any plans to, requesting |
| Billing | Payment, subscription, invoice, or pricing issues | Charge, invoice, payment, subscription, refund, upgrade, downgrade |
| Account | Account access, permissions, settings, or user management | Login, password, access, permission, SSO, locked out, can't sign in |
| Integration | Issues connecting to third-party tools or APIs | API, webhook, integration, connect, OAuth, sync, third-party |
| Security | Security concerns, data access, or compliance questions | Data breach, unauthorized, compliance, GDPR, SOC 2, vulnerability |
| Data | Data quality, migration, import/export issues | Missing data, export, import, migration, incorrect data, duplicates |
| Performance | Speed, reliability, or availability issues | Slow, timeout, latency, down, unavailable, degraded |
Category Determination Tips
- If the customer reports both a bug and a feature request, the bug is primary
- If they can't log in due to a bug, category is Bug (not Account) — root cause drives the category
- "It used to work and now it doesn't" = Bug
- "I want it to work differently" = Feature request
- "How do I make it work?" = How-to
- When in doubt, lean toward Bug — it's better to investigate than dismiss
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.
- 6d ago First seen · 185 lines · 52 tokens per session scan A 66519a688525
ticket-triage is a skill published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,725 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ticket-triage, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.