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/backup-health-check)<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.
<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>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 | $0.00005 | $0.00367 |
| Sonnet 5 | $0.00002 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00073 |
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 7d 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 — 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, andaxcient_get_job_historyavailable - The device's
device_id(fromaxcient_list_devicesoraxcient_list_devices_by_clientif not already known)
Steps
-
Pull device detail
Call
axcient_get_devicewithdevice_id. Extractcurrent_health_status,previous_health_status,type,product,d2c, and all threelatest_local_rp/latest_vault_rp/latest_cloud_rptimestamps. Note the device'sclient_idandjobsarray from the response — you'll need both for the next steps. -
Check AutoVerify
Call
axcient_get_device_autoverifywithdevice_id. This is the strongest recoverability signal available — a job can report success while producing an image that doesn't actually boot. Noteis_healthyand the timestamp of the last verification. -
Check recent job history
For each job ID in the device's
jobsarray, callaxcient_get_job_historywith the device'sclient_id,device_id, and thejob_id, using astarttime_begina 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 |
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.
- 7d ago First seen · 85 lines · 11 tokens per session scan A badeb4576861
backup-health-check is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 8d ago), licensed Apache-2.0. It adds 11 tokens to every session and 733 once invoked, about $0.0001 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 commands, from other repositories
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
deploy-to-render
Deploy the current project to Render.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.