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 | $0.00018 | $0.00431 |
| Sonnet 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 6d 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.
- 6d 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 (45 stars, last pushed 7d ago), licensed Apache-2.0. It adds 37 tokens to every session and 862 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-09-04.
Other skills, from other repositories
rented-server-setup
Runs an open model in the cloud two ways, and makes the user choose with real numbers. Route A is OVHcloud AI Endpoints, an EU-owned per-token API with zero idle cost, for spiky usage and EU jurisdiction. Route B rents one single-tenant RunPod GPU pod in a region the user picks, serving the model on vLLM behind a…
allow-team
Puts a running Open WebUI or Odysseus on a shareable public URL through an ngrok tunnel, so a teammate can sign in and use the local models without installing anything. Use when the user says "share Open WebUI with my team", "share Odysseus with my team", "let my colleague use my local AI", "expose Open WebUI", "share…
gcloud-cli-health-check
Run a Google Cloud CLI (gcloud) health check — verify installation, authentication, active project, recommended region, enabled APIs (run, cloudbuild, artifactregistry, secretmanager, cloudresourcemanager, iam, plus gmail/calendar/monitoring/logging), API access token, billing, IAM bindings, service accounts, and…
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…
terrakube-ops
Operate self-hosted Terrakube (remote OpenTofu/Terraform plan/apply, state, and workspace locking) — the canonical login/plan/apply workflow, why a targeted apply is dangerous, workspace lock recovery, the offline-mirror gotcha, and the token-rotation trap. Use when running or observing a Terrakube plan/apply…
openbao-dynamic-aws-creds
Replace a static AWS access key on a workstation or CI runner with short-lived STS credentials minted on demand by OpenBao's (or Vault's) AWS secrets engine, via an AWS credentialprocess wrapper. Covers the architecture, bring-up order, verification, plugin-upgrade caution, and common failure modes. Use when a…