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 ticketsgit 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/tickets)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/tickets"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/tickets/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/tickets"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/tickets.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.00026 | $0.02493 |
| Opus 5 | $0.00013 | $0.01247 |
| Sonnet 5 | $0.00005 | $0.00499 |
| Haiku 4.5 | $0.00003 | $0.00249 |
Grade A, and why
Atera Tickets 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 10d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atera Ticket Management
Overview
Atera tickets are the core unit of service delivery in the RMM/PSA platform. Every client request, incident, and service call flows through the ticketing system. This skill covers comprehensive ticket management including creation, updates, comments, and time tracking.
Anti-triggers
- The MSP's system-of-record helpdesk — plenty of shops run Atera
for RMM and a separate PSA for service desk. If tickets live
elsewhere, use
connectwise-psa-tickets,autotask-tickets,halopsa-tickets,syncro-tickets, orsuperops-tickets; a ticket created in the wrong system is a ticket nobody is watching. - The alert behind the ticket — alert-to-ticket conversion rules and
the alert side of that workflow are
atera-alerts.
Ticket Status Values
| Status | Description | Business Logic |
|---|---|---|
| Open | Newly created or reopened ticket | Default for new tickets |
| Pending | Awaiting customer response or information | SLA clock may pause |
| Resolved | Issue has been fixed | Awaiting customer confirmation |
| Closed | Ticket is complete | Final state, no further action |
Ticket Priority Levels
| Priority | Description | Typical SLA |
|---|---|---|
| Critical | Complete business outage | 1 hour response |
| High | Major productivity impact | 4 hour response |
| Medium | Single user/workaround exists | 8 hour response |
| Low | Minor issue/enhancement | 24 hour response |
Ticket Types
| Type | Description |
|---|---|
| Problem | Standard service issue |
| Request | Service request |
| Incident | Unplanned interruption |
| Change | Planned change |
Complete Ticket Field Reference
Core Fields
| Field | Type | Required | Description |
|---|---|---|---|
TicketID |
int | System | Auto-generated unique identifier |
TicketTitle |
string | Yes | Brief issue summary |
Description |
string | No | Detailed description |
TicketPriority |
string | No | Low, Medium, High, Critical |
TicketStatus |
string | No | Open, Pending, Resolved, Closed |
TicketType |
string | No | Problem, Request, Incident, Change |
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.
- 10d ago First seen · 350 lines · 26 tokens per session scan A d3674682a310
Atera Tickets is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 7d ago), licensed Apache-2.0. It adds 26 tokens to every session and 2,493 once invoked, about $0.0001 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
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…
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.
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.
collab-pm-report
A Korean-language assistant for creating weekly business review reports. A WBR is a regular meeting or report about results, ongoing work, plans, risks, and decisions.
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.
collab-vendor
A supplier-management guide for comparing vendors, organising contracts, and tracking risks in the supply chain. It also covers cross-border purchasing tasks such as customs documents and trade terms.