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 WYRE-AI/msp-claude-plugins --skill ticket-triage-agentgit clone --depth 1 https://github.com/WYRE-AI/msp-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/wyre-ai/msp-claude-plugins/ticket-triage-agent)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/ticket-triage-agent"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/ticket-triage-agent/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/wyre-ai/msp-claude-plugins/ticket-triage-agent"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/ticket-triage-agent.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.00061 | $0.01318 |
| Opus 5.5 | $0.00024 | $0.00527 |
| Sonnet 5.5 | $0.00012 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
Ticket Triage Agent 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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this does
Finds new/untriaged PSA tickets, classifies each by priority from its content, updates the record, moves it to In Progress, and posts a one-line summary to chat. Can run as a one-off right now, or be installed as an hourly Claude-managed scheduled routine.
Source
Generalizes the ticket-dispatcher agent (autotask plugin, Archetype
B — "the canonical archetype-B fit") plus the equivalent
service-desk-ops agents the catalog lists for halopsa and
connectwise-psa — the same three PSAs psa-tool-map curates tool
names for.
Prerequisites
| Requirement | Notes |
|---|---|
| A connected PSA | Autotask, HaloPSA, or ConnectWise PSA (curated — see psa-tool-map for tool names; another connected PSA works via guided discovery). Must be able to read and update tickets — priority and status. |
| A connected chat-delivery target | Slack (shipped) — see chat-delivery-adapters. Teams is not yet available. |
| Scheduled routines access (only if installing as a routine) | Via the /schedule capability; managed at claude.ai/code/routines. |
Detecting the customer's stack
- Check which curated PSA is connected. More than one → ask which to use. None → tell the human a PSA connection is needed, don't guess.
- Fetch
skill://advanced-workflows/psa-tool-map/SKILL.mdfor that vendor's exact tool names, status/priority discovery approach, and gotchas. - Fetch
skill://advanced-workflows/chat-delivery-adapters/SKILL.mdfor the connected delivery target's write tool and limits.
Run it now
- Using the PSA's "list new/untriaged tickets" tool, find tickets in the New (or equivalent untriaged) status.
- For each, get its detail (title, description, requester).
- Classify PRIORITY using the rubric below.
- Call the PSA's "update ticket" tool once per ticket: set priority AND advance status to In Progress in the same call — the status change is the idempotency guard, so a second run won't reprocess it.
- Post a one-line summary per ticket to the connected chat-delivery target.
- If an update call fails, leave the ticket in its original status and post a "needs a human" message instead — never skip silently.
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.
- 3d ago First seen · 121 lines · 61 tokens per session scan A 0df1ac68265f
Ticket Triage Agent is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 1,318 once invoked, about $0.0002 per session on Opus 5.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-10-13.
Other skills, from other repositories
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
project
A single starting point for setting up an AI-assisted project in Claude Cowork. It asks questions about the work, reviews available add-ons, and creates project instructions, custom agents, and connected workflows.
cs-escalation
A customer-support escalation manager for complaints, VIP cases, customer feedback, and recurring service problems. It assigns escalation levels, analyses the voice of the customer, and creates weekly support summaries.
hr-operations
A skill for designing remote-work and team-operation policies. It covers flexible work, asynchronous communication, collaboration tools, productivity tracking, and employee experience.
hr-performance-review
A skill for designing and running employee performance reviews. It covers MBO, OKRs, KPIs, 360-degree feedback, review guides, and feedback conversations; OKRs set goals and measurable results, while KPIs track ongoing performance.