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/create-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/create-ticket)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/create-ticket"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/create-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.00823 |
| Opus 5 | $0.00004 | $0.00411 |
| Sonnet 5 | $0.00002 | $0.00165 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
create-ticket 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 5d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Atera Ticket
Create a new service ticket in Atera with specified details.
Prerequisites
- Valid Atera API key configured
- Customer must exist in Atera
- User must have ticket creation permissions
Steps
-
Validate customer exists
- If numeric, use as customer ID directly
- If text, search customers by name
- Suggest similar names if no exact match
-
Check for duplicate tickets
- Search open tickets for same customer
- Warn if similar titles found in last 24 hours
-
Resolve optional fields
- Look up contact ID if contact provided
- Validate technician email if provided
- Apply default priority if not specified
-
Create the ticket
POST /api/v3/tickets X-API-KEY: {api_key} Content-Type: application/json { "TicketTitle": "<title>", "Description": "<description>", "EndUserID": <resolved_contact_id>, "TicketPriority": "<priority>", "TicketType": "Problem", "TechnicianContactID": <resolved_tech_id> } -
Return ticket details
- Ticket ID
- Ticket title
- Customer name
- Assigned technician
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| customer | string/int | Yes | - | Customer name or ID |
| title | string | Yes | - | Brief summary of the issue |
| description | string | No | - | Detailed issue description |
| priority | string | No | Medium | Low, Medium, High, Critical |
| contact | string | No | - | Contact name or email |
| technicianEmail | string | No | - | Technician to assign |
Examples
Basic Usage
/create-ticket "Acme Corp" "Email not working"
With Full Details
/create-ticket "Acme Corp" "Email not working" --description "Multiple users unable to send/receive since 9am" --priority High --contact "[email protected]" --technicianEmail "[email protected]"
Using Customer ID
/create-ticket 12345 "Server offline" --priority Critical
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.
- 5d ago First seen · 144 lines · 8 tokens per session scan A 34bbae668584
create-ticket is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 2d ago), licensed Apache-2.0. It adds 8 tokens to every session and 823 once invoked, about $0.0000 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 commands, from other repositories
research_codebase
Document codebase as-is with thoughts directory for historical context.
create_handoff
Create handoff document for transferring work to another session.
statusline-install
Add the backlog badge (📋 N open items) to the Claude Code statusLine. Wraps an existing statusLine if you have one, creates it otherwise. Edits /.claude/settings.json (or $CLAUDECONFIGDIR).
iterate_plan
Iterate on existing implementation plans with thorough research and updates.
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.