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 skills add WYRE-AI/msp-claude-plugins --skill alertsgit 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/skills/wyre-ai/msp-claude-plugins/alerts)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/alerts"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/alerts/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/alerts"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/alerts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 190 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00029 | $0.02629 |
| Opus 5 | $0.00015 | $0.01314 |
| Sonnet 5 | $0.00006 | $0.00526 |
| Haiku 4.5 | $0.00003 | $0.00263 |
Grade A, and why
Atera Alerts 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 9d 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atera Alert Management
Overview
Alerts in Atera are notifications generated when monitored systems exceed defined thresholds or encounter issues. They serve as the early warning system for MSPs, enabling proactive response to client issues before they become critical problems.
Anti-triggers
- The work the alert generated — an alert promoted into a service
desk record is a ticket; use
atera-tickets. - What raises the alert — thresholds and monitor configuration are
atera-devicesfor agentless monitors andatera-agentsfor endpoint health. - Alerts from a different RMM —
superops-alerts,ninjaone-alerts,datto-rmm-alerts,connectwise-automate-alerts, and N-central active issues (ncentral-monitoring-tasks) are separate stores with their own severity scales. Nothing here reads them, and the counts are not comparable. - A security detection — endpoint threat findings come from the EDR,
not the RMM; use
huntress-incidents,sentinelone-alerts, orrocketcyber-incidents.
Alert Severity Levels
| Severity | Description | Typical Response |
|---|---|---|
| Critical | Immediate action required | Respond within 15 minutes |
| Warning | Attention needed soon | Respond within 1 hour |
| Information | FYI, no action required | Review during normal hours |
Alert Sources
| Source | Description |
|---|---|
| Agent | Alerts from RMM agent monitoring |
| Device | Alerts from HTTP/SNMP/TCP monitors |
| Threshold | Alerts when metrics exceed limits |
| Custom | User-defined or API-created alerts |
Alert Types
| Type | Description | Common Triggers |
|---|---|---|
| Availability | Device/service up/down | Agent offline, ping failure |
| Performance | Resource utilization | High CPU, low memory, disk full |
| Hardware | Physical component issues | SMART errors, temperature |
| Security | Security-related events | Failed logins, malware detected |
| Application | Software issues | Service stopped, event log errors |
| Patch | Update status | Missing patches, update failures |
| Backup | Backup status | Backup failed, missed schedule |
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.
- 9d ago First seen · 336 lines · 29 tokens per session scan A 21bc943b065b
Atera Alerts is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 29 tokens to every session and 2,629 once invoked, about $0.0001 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 skills, from other repositories
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
content-card-news
A planning tool for four-card social media carousels on Instagram, Threads, and Kakao Channel, combining card copy, design guidance, image prompts, captions, and hashtags.
cs-voc-triage
A customer-feedback analysis tool that combines reviews and support contacts from multiple channels. VOC means “voice of the customer”: the comments, questions, complaints, and praise customers leave about a business.
design-copywriting
A copywriting workflow for marketing and product pages that uses a brand voice and returns structured text for page sections.
data-realestate
A lookup tool for reported South Korean property transactions using Ministry of Land data. It covers sales and rental deals for apartments, officetels, multi-family homes, houses, and commercial or office properties.
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.