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/resolve-alert)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/resolve-alert"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/resolve-alert.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.01299 |
| Opus 5 | $0.00004 | $0.00649 |
| Sonnet 5 | $0.00002 | $0.00260 |
| Haiku 4.5 | $0.00001 | $0.00130 |
Grade A, and why
resolve-alert 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 8d 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/alerts/{alert_id}" \ How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve Atera Alert
Resolve an RMM alert and optionally create an associated ticket for documentation.
Prerequisites
- Valid Atera API key configured
- Alert must exist and be in an open state
- User must have alert management permissions
Steps
-
Get alert details
curl -s -X GET "https://app.atera.com/api/v3/alerts/{alert_id}" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json"- Validate alert exists
- Capture alert details for ticket creation if needed
- Check if already resolved
-
Create ticket if requested If
--create_ticket true:curl -s -X POST "https://app.atera.com/api/v3/tickets" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "TicketTitle": "<ticket_title or alert title>", "Description": "Alert resolved: <alert details>\n\nResolution: <resolution_note>", "EndUserID": <customer_contact_id>, "TicketPriority": "<based on alert severity>", "TicketType": "Incident" }' -
Resolve the alert
curl -s -X POST "https://app.atera.com/api/v3/alerts/{alert_id}/resolve" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "ResolutionNote": "<resolution_note>" }' -
Return resolution confirmation
- Alert ID and original title
- Resolution timestamp
- Resolution note
- Ticket ID if created
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| alert_id | integer | Yes | - | The alert ID to resolve |
| resolution_note | string | No | - | Description of the resolution |
| create_ticket | boolean | No | false | Create a ticket from this alert |
| ticket_title | string | No | - | Custom title for the ticket |
Examples
Simple Resolution
/resolve-alert 9876
Resolution with Note
/resolve-alert 9876 --resolution_note "Disk space issue resolved by cleanup script"
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.
- 8d ago First seen · 229 lines · 8 tokens per session scan A cb4250dd6a72
resolve-alert 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,299 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
resolve-codeql
Analyze and resolve CodeQL alerts systematically.
site-audit
Crawl a website and audit for broken links, spelling errors, console errors, and visual issues.
check
Run static analysis on the Java project — detects configured tools (Checkstyle, SpotBugs, PMD) and reports findings.
analyze-issue
A command that runs a systematic problem investigation and searches for the root cause through a five-agent analysis process.
quick-analyze
A command for quickly analysing a problem when you already have a clear error message.
checklist
Generate a custom checklist for the current feature based on user requirements.