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 clientsgit 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/clients)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/clients"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/clients/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/clients"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/clients.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.00050 | $0.01445 |
| Opus 5 | $0.00025 | $0.00723 |
| Sonnet 5 | $0.00010 | $0.00289 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
Axcient Clients 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 5d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Axcient Clients
Overview
A "client" in x360Recover is the tenant/customer boundary — roughly equivalent to a PSA company. Every device, job, vault, and appliance belongs to exactly one client. Client health is a rollup Axcient computes from the devices underneath it, not a value you set.
Tools
| Tool | Description | Arguments |
|---|---|---|
axcient_list_clients |
Every client visible to this credential | include_appliances? |
axcient_get_client |
One client's detail | client_id, include_appliances? |
axcient_get_d2c_agent_token |
Mint a D2C agent enrollment token | client_id, vault_id |
List Clients
axcient_list_clients
Example response (one client):
{
"id": 26,
"name": "Acme Corp",
"client_code": "ACME",
"active": true,
"health_status": "NORMAL",
"devices_counters": {
"appliance_based": [
{ "type": "SERVER", "count": 0 },
{ "type": "WORKSTATION", "count": 4 }
],
"d2c": [
{ "type": "SERVER", "count": 2 },
{ "type": "WORKSTATION", "count": 7 }
],
"cloud_archive": [
{ "type": "SERVER", "count": 2 },
{ "type": "WORKSTATION", "count": 0 }
]
}
}
Protected-System Counters
devices_counters breaks the client's protected systems into three
independent buckets, each split by SERVER/WORKSTATION:
| Bucket | Meaning |
|---|---|
appliance_based |
Backed up to a local Axcient appliance |
d2c |
Direct-to-cloud — no local appliance, agent replicates straight to Axcient's cloud |
cloud_archive |
Long-term cloud archive copies |
A device can appear in more than one bucket (e.g. appliance-based and cloud-archived via vault replication). Sum the buckets to get a client's total protected-system count; do not assume they're mutually exclusive.
Client Health Status
health_status is a client-level rollup (values observed: NORMAL, and
presumably WARNED/CRITICAL mirroring the device-level status model — see
the devices skill). It reflects the worst device under that client, not an
independently-computed value. To find which device is dragging a client's
health down, call axcient_list_devices_by_client and inspect each
device's own current_health_status.
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.
- 5d ago First seen · 158 lines · 50 tokens per session scan A ca0a43465709
Axcient Clients is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,445 once invoked, about $0.0003 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…
homelab-runbooks
Use when powering on a sleeping DR node, converging DNS records for a new ingress vhost, or bringing up OpenBao/Terrakube JWT identity — homelab operational runbooks for power management, DNS, and secrets-engine bring-up.
proxmox-cluster-ops
Operate a Proxmox VE cluster safely — read-only inspection with pvesh/pct/qm/pvecm instead of hand-editing a live guest, node-by-node package updates that respect quorum, and the shape of joining a new node to an existing cluster. Use when inspecting cluster or guest state, planning a rolling update across cluster…