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 appliancesgit 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/appliances)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/appliances"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/appliances/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/appliances"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/appliances.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00862 |
| Opus 5.5 | $0.00015 | $0.00345 |
| Sonnet 5.5 | $0.00007 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
Axcient Appliances 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 2mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Axcient Appliances
Overview
An appliance is the physical or virtual box running local backups for appliance-based devices (as opposed to direct-to-cloud devices, which have no appliance at all). Every appliance-based device belongs to exactly one appliance; D2C devices never appear under one.
Anti-triggers
- A D2C-only device — it has no appliance and won't appear in any
appliance's device list. Use the
devicesskill directly. - Vault capacity — an appliance's local storage is separate from vault
storage; see the
vaultsskill for replication-target capacity.
Tools
| Tool | Description | Arguments |
|---|---|---|
axcient_list_appliances |
Every appliance in the organization | service_id?, include_devices? |
axcient_list_appliances_by_client |
Appliances for one client | client_id, include_devices? |
axcient_get_appliance |
One appliance's detail | appliance_id, include_devices? |
include_devices defaults to true on all three — pass false
explicitly when you only need appliance-level fields and want a smaller
response for a large fleet.
Service ID Filtering
axcient_list_appliances accepts an optional service_id — the
appliance's 4-character serial/service identifier, useful when a
technician has the physical unit's ID label in hand but not its
client_id.
Common Workflows
Appliance Inventory for a Client
axcient_list_appliances_by_clientwith the client's ID- For each appliance, note model/version fields and the attached device
count (from the embedded device list, if
include_deviceswas left at its defaulttrue)
Locating an Appliance by Serial
axcient_list_applianceswithservice_idset to the label on the physical unit- If nothing matches, the unit may be decommissioned or the service ID
was misread — cross-check with
axcient_list_clientsfor the expected client instead of assuming the appliance doesn't exist in the API
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.
- 2mo ago First seen · 97 lines · 37 tokens per session scan A 3731d2f01570
Axcient Appliances is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (52 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 862 once invoked, about $0.0001 per session on Opus 5.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-09-04.
Axcient Appliances compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| Axcient AppliancesWYRE-AI/msp-claude-plugins | Skill | 52 | today | Apache-2.0 | A | 37 | Claude Code |
| rented-server-setupnaveedharri/benai-skills | Skill | 80 | 1mo ago | MIT | A | 258 | Claude Code |
| allow-teamnaveedharri/benai-skills | Skill | 80 | 1mo ago | MIT | A | 181 | Claude Code |
| gcloud-cli-health-checkMSApps-Mobile/claude-plugins | Skill | 11 | today | MIT | A | 175 | Claude Code |
| cloudflare-managerckorhonen/claude-skills | Skill | 26 | 1mo ago | MIT | A | 69 | Claude Code |
| aws-spa-deployziniman/ai-instruct | Skill | 29 | 19d ago | Apache-2.0 | A | 142 | Claude Code |
| dell-idrac-bmc-opsdryvist/claude-code-plugins | Skill | 3 | today | Apache-2.0 | A | 67 | Claude Code |