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 jeremylongworth-source/AgentSkills --skill ticket-triagegit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/ticket-triage)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/ticket-triage"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/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/jeremylongworth-source/agentskills/ticket-triage"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/ticket-triage.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.00049 | $0.00397 |
| Opus 5 | $0.00024 | $0.00198 |
| Sonnet 5 | $0.00010 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00040 |
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 7d 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.
What it actually says
Ticket Triage
Core Workflow
- Separate customer facts from assumptions, guesses, and internal notes.
- Identify customer goal, product area, account or plan context, impact, urgency, sentiment, and requested outcome.
- Classify the ticket by type: how-to, bug, billing, access, data, incident, security, feature request, cancellation, renewal, or feedback.
- Assign severity using the supplied support policy or escalation rules. If no policy is available, label severity as provisional and explain why.
- Identify missing information needed to resolve or route the ticket.
- Recommend owner, next action, and whether a reply draft, escalation pack, or KB draft is appropriate.
Safety Rules
- Do not promise refunds, SLAs, incident status, fixes, timelines, or policy exceptions.
- Do not recommend account, billing, entitlement, or data changes without approval.
- Do not ask customers to send passwords, secrets, tokens, full payment data, or unredacted sensitive logs.
- Escalate security, privacy, legal, payment, data-loss, production outage, and high-value customer risks.
Deliverable Shape
For ticket triage, provide:
- Customer issue summary
- Ticket type and product area
- Impact, urgency, and sentiment
- Severity with rationale
- Known facts and missing information
- Recommended owner
- Next action
- Escalation or reply-drafting notes
References
- Read
references/ticket-triage-checklist.mdwhen triaging a support request or creating a support queue review.
What ships with it
2 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.
- 7d ago First seen · 50 lines · 49 tokens per session scan A 82bccc5e2874
ticket-triage is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 397 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-09-03.
Other skills, from other repositories
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…
kelly-followups
Busabase-backed App-in-Skill for one thing only — record who you need to follow up with after a meeting, see what is due today, mark it done. Use when the user invokes $kelly-followups or /kelly-followups, mentions a followup, follow-up, meeting action item, or wants a lightweight daily reminder of who to check in…
syncfusion-maui-kanban-board
Implements Syncfusion .NET MAUI Kanban Board (SfKanban) control. Use when implementing kanban boards, task management visualizations, workflow tracking, or agile boards in .NET MAUI applications. Covers installation, data binding with default and custom models, card customization, column configuration, workflow…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
lark-calendar
A tool for managing Feishu calendars and events, including meetings, attendees, room bookings, and availability checks.