Axcient Devices skillA
Axcient Devices is agent-read markdown (skill) from wyre-ai/msp-claude-plugins: Axcient x360Recover protected devices (servers and workstations): SERVER/WORKSTATION typing, the current/previous health-status model, local vs vault vs cloud usage and recovery-point timestamps, AutoVerify screenshot verification, and restore points..
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
# Axcient Devices ## Overview A device is one protected server or workstation — either backed up through a local appliance or replicating directly to the cloud (D2C). Devices carry their own health status, usage figures across up to three storage tiers (local appliance, private vault, Axcient cloud), and the list of backup jobs running against them. ## Anti-triggers - **The appliance itself (hardware/capacity)** — use the `appliances` skill; a device is what's *protected*, an appliance is what's *doing the protecting*. - **A specific backup run's pass/fail history** — device-level `latest_*_rp` fields are point-in-time snapshots, not history. Use the `jobs` skill's `axcient_get_job_history` for that. ## Tools | Tool | Description | Arguments | |------|-------------|-----------| | `axcient_list_devices` | Every device across the organization | `limit?`, `offset?` | | `axcient_list_devices_by_client` | Devices for one client | `client_id`, `service_id?`, `d2c_only?` | | `axcient_get_device` | Full detail for one device | `device_id` | | `axcient_get_device_autoverify` | Latest AutoVerify (screenshot boot-test) results | `device_id` | …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Axcient Devices@git:20260819.8b2451cmdr add wyre-ai/msp-claude-plugins/Axcient Devices@sha256:994edb466bab2b44Pin 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_uyyepap4cnu5imjl)
1 badge views in 30 days
Versions
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 (7303 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_uyyepap4cnu5imjl GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Axcient Devices GET https://markdownregistry.com/api/v1/blob/994edb466bab2b4471177843ed89edb6a1afc413038c2e807bd547125d9981fb
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.