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/get-ticket)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/get-ticket"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/get-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.01647 |
| Opus 5 | $0.00004 | $0.00823 |
| Sonnet 5 | $0.00002 | $0.00329 |
| Haiku 4.5 | $0.00001 | $0.00165 |
Grade A, and why
get-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 4d 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 \ How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get ConnectWise PSA Ticket
Retrieve detailed ticket information including status, notes, time entries, and configuration items.
Prerequisites
- Valid ConnectWise PSA API credentials configured
- User must have ticket read permissions
Steps
-
Validate ticket exists
- Fetch ticket by ID
- Handle 404 if ticket not found
- Check user has access to view ticket
-
Retrieve base ticket information
GET /service/tickets/{id}- Include company, contact, status, priority, board details
- Parse SLA information if available
-
Fetch ticket notes (if include_notes=true)
GET /service/tickets/{id}/notes?pageSize=100&orderBy=dateCreated desc- Retrieve all notes with author and timestamp
- Distinguish internal vs external notes
-
Fetch time entries (if include_time=true)
GET /service/tickets/{id}/timeentries?pageSize=100&orderBy=timeStart desc- Calculate total hours logged
- Show billable vs non-billable breakdown
-
Fetch configurations (if include_configs=true)
GET /service/tickets/{id}/configurations?pageSize=100- List associated assets/devices
- Include configuration type and status
-
Fetch tasks (if include_tasks=true)
GET /service/tickets/{id}/tasks?pageSize=100&orderBy=sequence- Show task list with completion status
- Include estimated vs actual time
-
Format and return comprehensive ticket view
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| ticket_id | integer | Yes | - | ConnectWise ticket ID |
| include_notes | boolean | No | true | Include ticket notes |
| include_time | boolean | No | false | Include time entries |
| include_configs | boolean | No | false | Include configuration items |
| include_tasks | boolean | No | false | Include service tasks |
Examples
Basic Usage
/get-ticket 12345
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.
- 4d ago First seen · 273 lines · 8 tokens per session scan A 1444bd2ef4c2
get-ticket is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,647 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-09-04.
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.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.