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 backup-job-healthgit 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/backup-job-health)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/backup-job-health"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/backup-job-health/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/backup-job-health"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/backup-job-health.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.00101 | $0.01962 |
| Opus 5 | $0.00051 | $0.00981 |
| Sonnet 5 | $0.00020 | $0.00392 |
| Haiku 4.5 | $0.00010 | $0.00196 |
Grade A, and why
Backup Job Health 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 8d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backup Job Health
Overview
"Backups are running" is the single most-assumed, least-verified fact in an MSP's environment. A backup job that failed silently three nights ago looks identical, from a distance, to one that's been succeeding for months — nobody notices until a restore is needed and there's nothing current to restore from. This skill is the recurring, portfolio-wide sweep that catches that gap before it becomes an incident: job success/ failure rate, missed-backup detection, and storage-consumption trending, rolled into one normalized view across every backup and BCDR tool an org has connected.
This skill is about whether backups are happening. It is deliberately narrower than
disaster-recovery readiness as a whole — it does not assess whether a backup, once
taken, is actually recoverable (see restore-test-verification), and it does not
assess whether the retention window or cadence in place actually satisfies a
contracted requirement (see retention-rpo-compliance). Treat this as the first,
most frequent layer of the DR assurance stack: if jobs aren't running, nothing
downstream matters yet.
Anti-triggers
- Backup Radar's own health records — ScalePad already aggregates and
scores backup results across vendors; use
scalepad-backup-radarwhen the question is what that API returns. This skill normalizes across every connected backup tool, including orgs that have no Backup Radar at all. - One platform's job, alert, or storage data — use
datto-bcdr-api-patterns,datto-saas-protection-api-patterns,spanning-api-patterns, orunitrends-api-patternsfor a single vendor's request shapes and field names.
Key Concepts
Two fundamentally different job models
Backup and BCDR vendors protect data in two structurally different ways, and treating them as the same "job" concept produces misleading comparisons:
- Image-based appliance backup (e.g. Datto BCDR / SIRIS / Alto, Unitrends) —
protects physical or virtual servers/workstations by taking periodic block-level
or image-level snapshots to a local appliance, then syncing offsite/to the cloud.
A "job" here is a scheduled backup of one protected agent/asset on one appliance.
Health signals include: last successful local backup, last successful offsite
sync, and (for Datto BCDR specifically) screenshot/boot verification status —
see
restore-test-verification. - SaaS-data snapshot backup (e.g. Datto SaaS Protection, Spanning) — protects cloud application data (Microsoft 365 mailboxes/OneDrive/SharePoint/Teams, Google Workspace, Salesforce) by taking periodic API-level snapshots of tenant data. A "job" here is a scheduled backup pass across a set of protected seats/users for a tenant. There is no "appliance" and no local/offsite sync distinction — health signals are seat coverage (are all licensed users actually being backed up) and per-run success/failure across the tenant.
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.
- 8d ago First seen · 169 lines · 101 tokens per session scan A 219f87c7b406
Backup Job Health is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 9d ago), licensed Apache-2.0. It adds 101 tokens to every session and 1,962 once invoked, about $0.0005 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
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
design-copywriting
A copywriting workflow for marketing and product pages that uses a brand voice and returns structured text for page sections.
content-card-news
A planning tool for four-card social media carousels on Instagram, Threads, and Kakao Channel, combining card copy, design guidance, image prompts, captions, and hashtags.
cs-voc-triage
A customer-feedback analysis tool that combines reviews and support contacts from multiple channels. VOC means “voice of the customer”: the comments, questions, complaints, and praise customers leave about a business.
lead-intelligence
Deep-research lead intelligence gathering for B2B qualified leads. This skill runs in two layers.