What is backup-health-check?

A procedure for checking one Axcient-protected device's backup health and recoverability. It includes recent backup points, AutoVerify boot testing, and job run history.

Use it to inspect device status, check recovery-point freshness across storage tiers, review AutoVerify results, and examine recent backup runs.

A successful backup job does not by itself prove that the backed-up system can boot, so the check also examines verification results.

backup-health-check — Command for Claude Code by WYRE-AI

Install

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.

Clone the repo

git clone --depth 1 https://github.com/WYRE-AI/msp-claude-plugins

Made for: Claude Code.

Or install axcient, the plugin that ships this one along with the rest of its 4 skills, 2 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/backup-health-check/github.svg)](https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/backup-health-check)

Your own site

<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/backup-health-check"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/backup-health-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/backup-health-check"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/backup-health-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 733 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00011	$0.00733
Opus 5.5	$0.00004	$0.00293
Sonnet 5.5	$0.00002	$0.00147
Haiku 4.5	$0.00001	$0.00073

Measured 2mo ago against content hash badeb4576861, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

backup-health-check 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.

msp-claude-plugins/axcient/axcient/commands/backup-health-check.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Backup Health Check

Full health check for one Axcient x360Recover device: current status, recovery-point freshness across all storage tiers, AutoVerify boot-test result, and recent job run history.

Prerequisites

Axcient MCP server connected with a valid API key
MCP tools axcient_get_device, axcient_get_device_autoverify, and axcient_get_job_history available
The device's device_id (from axcient_list_devices or axcient_list_devices_by_client if not already known)

Steps

Pull device detail

Call axcient_get_device with device_id. Extract current_health_status, previous_health_status, type, product, d2c, and all three latest_local_rp / latest_vault_rp / latest_cloud_rp timestamps. Note the device's client_id and jobs array from the response — you'll need both for the next steps.
Check AutoVerify

Call axcient_get_device_autoverify with device_id. This is the strongest recoverability signal available — a job can report success while producing an image that doesn't actually boot. Note is_healthy and the timestamp of the last verification.
Check recent job history

For each job ID in the device's jobs array, call axcient_get_job_history with the device's client_id, device_id, and the job_id, using a starttime_begin a few days back. Look for a pattern of failures rather than a single missed run.
Synthesize

Report:
- Overall status (healthy / degraded / stale / unknown)
- Which of the three recovery-point tiers (local/vault/cloud) are current vs. stale, with actual timestamps
- Whether AutoVerify confirms the latest recovery point boots
- Any job showing a recent failure pattern, with the job name/ID
Do not report "backed up" as a single yes/no — state each tier's freshness explicitly, since a device can be current locally while its cloud or vault replication has silently stalled.

Parameters

Parameter	Type	Required	Description
device_id	integer	Yes	The Axcient device to check

Read the full file on GitHub · 85 lines

Changes

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 · 85 lines · 11 tokens per session scan A badeb4576861

Subscribe to this mod's changes

backup-health-check is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (52 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 733 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.

Claude Code Cloud DevOps and cloud claude claude-plugins msp psa rmm

backup-health-check next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
backup-health-checkWYRE-AI/msp-claude-plugins	Command	52	today	Apache-2.0	A	11	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