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 agentmods add commands/wyre-ai/msp-claude-plugins/close-ticketgit 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/close-ticket)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/close-ticket"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/close-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.00009 | $0.02140 |
| Opus 5 | $0.00005 | $0.01070 |
| Sonnet 5 | $0.00002 | $0.00428 |
| Haiku 4.5 | $0.00001 | $0.00214 |
Grade A, and why
close-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 2d 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 POST \ How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close ConnectWise PSA Ticket
Close a ConnectWise ticket with resolution notes and optional time entry.
Prerequisites
- Valid ConnectWise PSA API credentials configured
- User must have ticket update permissions
- Ticket must exist and be accessible
- A valid closed status must exist on the ticket's board
Steps
-
Validate ticket exists and get current state
GET /service/tickets/{id}- Confirm ticket is accessible
- Get current board ID for status lookup
- Check if ticket is already closed
-
Resolve closed status
GET /service/boards/{boardId}/statuses?conditions=closedStatus=true- If status parameter provided, validate it's a closed status
- Otherwise, use board's default closed status
-
Add resolution note
POST /service/tickets/{id}/notes Content-Type: application/json { "text": "<resolution>", "resolutionFlag": true, "internalAnalysisFlag": false, "customerUpdatedFlag": true, "processNotifications": true } -
Log time entry (if time_minutes provided)
POST /time/entries Content-Type: application/json { "chargeToId": <ticket_id>, "chargeToType": "ServiceTicket", "timeStart": "<current_datetime>", "timeEnd": "<current_datetime + time_minutes>", "actualHours": <time_minutes / 60>, "notes": "<time_notes or resolution>", "billableOption": "<Billable or DoNotBill>" } -
Update ticket status to closed
PATCH /service/tickets/{id} Content-Type: application/json [ {"op": "replace", "path": "/status/id", "value": <closed_status_id>}, {"op": "replace", "path": "/resolution", "value": "<resolution>"} ] -
Return closure confirmation
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| ticket_id | integer | Yes | - | ConnectWise ticket ID to close |
| resolution | string | Yes | - | Resolution notes |
| status | string | No | Board default | Closed status name |
| time_minutes | integer | No | - | Final time entry in minutes |
| time_notes | string | No | - | Notes for time entry |
| billable | boolean | No | true | Mark time as billable |
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.
- 2d ago First seen · 334 lines · 9 tokens per session scan A 8702db2d6c20
close-ticket is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 3d ago), licensed Apache-2.0. It adds 9 tokens to every session and 2,140 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
speckit.verify-tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
speckit.git.initialize
Initialize a Git repository with an initial commit.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.