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.
git 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/commands/wyre-ai/msp-claude-plugins/update-ticket)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/update-ticket"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/update-ticket.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.00008 | $0.01148 |
| Opus 5 | $0.00004 | $0.00574 |
| Sonnet 5 | $0.00002 | $0.00230 |
| Haiku 4.5 | $0.00001 | $0.00115 |
Grade A, and why
update-ticket scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X GET "https://app.atera.com/api/v3/tickets/{ticket_id}" \ How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Atera Ticket
Update fields on an existing Atera ticket including status, priority, technician assignment, and ticket type.
Prerequisites
- Valid Atera API key configured
- Ticket must exist in Atera
- User must have ticket update permissions
Steps
-
Validate ticket exists
curl -s -X GET "https://app.atera.com/api/v3/tickets/{ticket_id}" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json"- Return error if ticket not found (404)
- Store current ticket state for comparison
-
Resolve technician if provided
curl -s -X GET "https://app.atera.com/api/v3/technicians" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json"- Search for technician by email
- Return error if technician not found
-
Build update payload
- Only include fields that are being changed
- Map status to Atera status values
- Map priority to Atera priority values
-
Update the ticket
curl -s -X PUT "https://app.atera.com/api/v3/tickets/{ticket_id}" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "TicketStatus": "<status>", "TicketPriority": "<priority>", "TechnicianContactID": <tech_id>, "TicketType": "<ticket_type>", "TicketImpact": "<impact>" }' -
Return updated ticket details
- Ticket ID and title
- Changed fields with before/after values
- Direct link to ticket
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| ticket_id | integer | Yes | - | The Atera ticket ID to update |
| status | string | No | - | Open, Pending, Resolved, Closed |
| priority | string | No | - | Low, Medium, High, Critical |
| technician_email | string | No | - | Email of technician to assign |
| ticket_type | string | No | - | Problem, Request, Incident, Change |
| impact | string | No | - | Minor, Major, Crisis, No Impact |
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 · 203 lines · 8 tokens per session scan A 73d895b0da61
update-ticket is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 4d ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,148 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
project
A command-style entry point for initializing a project with an interview, custom agents, skill workflows, and project instruction files. It also supports update, evolution, and diagnostic modes.
resume_handoff
Resume work from handoff document with context analysis and validation.
factory
Run one pass of the ticket queue — scan the tracker for human-authorized tickets, claim one, and route it to the right workflow (spec a raw ticket, groom the backlog, hunt a bug, or build an approved spec in its own worktree via /sonu:build). You are the trigger; there is no daemon. Never merges and never authorizes…
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.