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.
git 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/commands/wyre-ai/msp-claude-plugins/client-backup-overview)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/client-backup-overview"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/client-backup-overview/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/commands/wyre-ai/msp-claude-plugins/client-backup-overview"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/client-backup-overview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00012 | $0.00568 |
| Opus 5.5 | $0.00005 | $0.00227 |
| Sonnet 5.5 | $0.00002 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
client-backup-overview 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Backup Overview
Rolls up backup health across every device for one Axcient x360Recover client — the fastest way to answer "is this customer's backup posture okay" without checking each device one at a time.
Prerequisites
- Axcient MCP server connected with a valid API key
- MCP tools
axcient_get_clientandaxcient_list_devices_by_clientavailable
Steps
-
Pull client summary
Call
axcient_get_clientwithclient_id. Notehealth_statusanddevices_counters(appliance_based / d2c / cloud_archive, each split by SERVER/WORKSTATION) as the baseline expectation for device count. -
List devices
Call
axcient_list_devices_by_clientwith the sameclient_id. For each device, capturename,type,current_health_status, and the threelatest_*_rptimestamps. -
Flag outliers
Identify devices where:
current_health_status.statusis not the healthy value- Any
latest_*_rplooks stale relative to the device's configured thresholds (thresholds.*_rp_thresholdon the device detail — callaxcient_get_deviceon flagged devices for the full threshold object) - The device count from step 2 doesn't match the sum of
devices_countersbuckets from step 1 (worth a note, not necessarily an error — buckets aren't mutually exclusive)
-
Report
Present a table: device name, type, health status, most-stale recovery-point tier and its age. Lead with anything unhealthy or stale; don't bury outliers in a full device list. For any flagged device, suggest
/backup-health-checkfor the deeper AutoVerify + job-history dive.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| client_id | integer | Yes | The Axcient client to overview |
Examples
/client-backup-overview --client_id 26
Error Handling
- Client Not Found: Verify against
axcient_list_clients. - Empty Device List: A client with zero devices under it is a valid
(if unusual) state — confirm the client is active (
active: true) before treating this as an error.
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 · 74 lines · 12 tokens per session scan A bc73e65baa7c
client-backup-overview is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (52 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 568 once invoked, about $0.0000 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.
client-backup-overview compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| client-backup-overviewWYRE-AI/msp-claude-plugins | Command | 52 | today | Apache-2.0 | A | 12 | Claude Code |
| ship-deploymentcomposio-community/awesome-claude-plugins | Command | 2.0k | 5d ago | none | A | 0 | Claude Code |
| backup-setupMSApps-Mobile/claude-plugins | Command | 11 | today | MIT | A | 10 | Claude Code |
| backup-statusMSApps-Mobile/claude-plugins | Command | 11 | today | MIT | A | 10 | Claude Code |
| backup-nowMSApps-Mobile/claude-plugins | Command | 11 | today | MIT | A | 15 | Claude Code |
| lb-createTheLobbi/Claude-m | Command | 19 | 1mo ago | none | A | 19 | Claude Code |
| setupzircote/terraform-lsp | Command | 2 | 7d ago | MIT | D | 0 | Claude Code |