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 devicesgit 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/devices)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/devices"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/devices.svg" alt="Measured on agentmods" 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 252 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.00037 | $0.02980 |
| Opus 5 | $0.00018 | $0.01490 |
| Sonnet 5 | $0.00007 | $0.00596 |
| Haiku 4.5 | $0.00004 | $0.00298 |
Grade A, and why
Atera Devices 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 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.
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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atera Device Monitoring
Overview
Atera device monitors extend monitoring capabilities beyond agent-based endpoints to include network devices, services, and applications. These agentless monitors use HTTP, SNMP, and TCP protocols to check availability and gather metrics.
Anti-triggers
- A workstation or server running the Atera agent — that is an agent
record, not a device monitor; use
atera-agents. This is the single most common misroute in this plugin, because "device" means the managed endpoint in every other RMM here. - The alert a monitor fired — monitor configuration and thresholds
live here; the acknowledge/resolve lifecycle is
atera-alerts. - Network discovery, topology, or interface statistics as a product
— use
auvik-devicesorauvik-networks; this skill only configures Atera's own HTTP, SNMP, and TCP checks.
Monitor Types
HTTP Monitors
Monitor web services and applications via HTTP/HTTPS requests.
| Feature | Description |
|---|---|
| Protocol | HTTP or HTTPS |
| Methods | GET, POST, HEAD |
| Validation | Status code, response content |
| Authentication | Basic, custom headers |
| Use Cases | Websites, APIs, web apps |
SNMP Monitors
Monitor network devices using Simple Network Management Protocol.
| Feature | Description |
|---|---|
| Versions | SNMP v1, v2c, v3 |
| Operations | GET, GETNEXT, WALK |
| Data Types | OIDs, MIBs, counters |
| Use Cases | Routers, switches, firewalls, printers |
TCP Monitors
Monitor service availability via TCP port connectivity.
| Feature | Description |
|---|---|
| Protocol | TCP |
| Check Type | Port open/closed |
| Response | Connection success/timeout |
| Use Cases | Custom services, databases, mail servers |
Device Monitor Fields
Common Fields
| Field | Type | Description |
|---|---|---|
DeviceID |
int | Unique device identifier |
CustomerID |
int | Associated customer ID |
CustomerName |
string | Customer display name |
DeviceName |
string | Monitor display name |
DeviceType |
string | HTTP, SNMP, TCP |
Hostname |
string | Target host/IP address |
Online |
boolean | Current status |
LastSeen |
datetime | Last successful check |
CreatedOn |
datetime | Monitor creation date |
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 · 384 lines · 37 tokens per session scan A 52204ae26b4e
Atera Devices is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 37 tokens to every session and 2,980 once invoked, about $0.0002 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
scan-my-machine
Scans the user's actual hardware and tells them exactly which local AI models they can run, by name, with expected speed. Use when the user asks "what models can my computer run", "can I run a local LLM", "how much VRAM do I have", "which model should I download", "is my Mac good enough for local AI", "scan my…
dell-idrac-bmc-ops
Bring a Dell PowerEdge BMC (iDRAC) onto the network headlessly, standardize its baseline settings, stage its firmware, and drive an unattended Proxmox/Linux install through it — including generation-specific Redfish/racadm gotchas, the identity-before-power-action rule, and the phantom-drive failure mode caused by…
pxe-netboot
Reliable remote OS install over PXE when a server's virtual-media/remote-KVM path is broken or unreliable — proxyDHCP + TFTP via dnsmasq, kernel/initrd served over plain HTTP, and a custom-built iPXE binary with an embedded autoexec script (because a distro-packaged one won't auto-chainload). Use when a legacy BMC's…
ha-addon-scaffold
Scaffold a production-ready Home Assistant add-on: config.yaml with UI options schema, multi-arch Dockerfile + build.yaml, s6-overlay services, Ingress web UI wiring, GHCR CI, DOCS/CHANGELOG, and an add-on repository.yaml. Use when creating a new Home Assistant add-on, adding an add-on to a repository, or setting up…
automatic-cybernetic-flow-design
Use when the user wants a cybernetic flow design document for an interactive system. Specifies sensors, actuators, feedback paths, delays, and oscillation risk, and writes the design to a named local file. Not for implementing or deploying the system.
akg-agents
An agent workflow for developing, generating, testing, and tuning AKG operators. AKG is a toolkit for generating optimized computational kernels.