Auvik Devices skillA
Auvik Devices is agent-read markdown (skill) from wyre-ai/msp-claude-plugins: Auvik device records: device types, manageStatus and onlineStatus, lifecycle and warranty fields, and choosing between the v1 list endpoint and the detailed device endpoints..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Auvik Devices Devices are the unit of inventory in Auvik. Every discovered piece of network gear or endpoint - whether actively monitored or just seen on a discovery scan - has a device record. This skill covers the device type taxonomy, the manage-status model, lifecycle fields, and which tool to call for which question. ## Anti-triggers - **Changing the device, not just reading it** — Auvik is a monitoring and documentation layer and never pushes configuration. On Meraki hardware use `meraki-devices`; for MX firewall or VPN changes, `meraki-security-appliance`. - **A per-site sweep of everything with an IP** — Auvik indexes infrastructure it can poll. The collector that fingerprints every host on a local subnet, including phones and IoT gear, is `domotz-devices`. - **Hunting unknown assets as a security exercise** — Auvik's `unmanaged` means "discovered but not polled", not "unaccounted for". Attack-surface and rogue-asset discovery is `runzero`. - **Whether a device is alerting right now** — the device record carries status, not the alert queue; use `auvik-alerts`. ## Tools | Tool | Use For | |------|---------| …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Auvik Devices@git:20260804.055e86emdr add wyre-ai/msp-claude-plugins/Auvik Devices@sha256:3b3395424a1ba7efPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_4owgqguwsjbh2mdc)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.055e86e latest | 2026-08-04 | 055e86e | 6,365 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 5,576 B | A | view · diff |
| git:20260713.1fbd3f3 | 2026-07-13 | 1fbd3f3 | 5,628 B | A | view · diff |
| git:20260521.b3d675e | 2026-05-21 | b3d675e | 5,645 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6365 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wyre-ai/msp-claude-plugins · 46 stars · license Apache-2.0 · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4owgqguwsjbh2mdc GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Auvik Devices GET https://markdownregistry.com/api/v1/blob/3b3395424a1ba7ef7954df203c560ececb9803440f0b808f6ee8a5bd9fdbd789
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.