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 vaultsgit 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/vaults)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/vaults"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/vaults/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/vaults"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/vaults.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.00056 | $0.01192 |
| Opus 5.5 | $0.00022 | $0.00477 |
| Sonnet 5.5 | $0.00011 | $0.00238 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
Axcient Vaults 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Axcient Vaults
Overview
A vault is a replication target — either a Private vault (customer- or
partner-owned on-prem storage) or a Cloud vault (Axcient-hosted). Devices
replicate to one or more vaults; a vault's storage_details reports how
much of its capacity is in use.
Tools
| Tool | Description | Arguments |
|---|---|---|
axcient_list_vaults |
Every vault visible to this credential | vault_type? (Private|Cloud), active?, with_url?, limit?, include_devices? |
axcient_get_vault |
One vault's detail | vault_id |
axcient_get_vault_threshold |
Current connectivity-loss threshold | vault_id |
axcient_set_vault_threshold |
Changes the connectivity-loss threshold | vault_id, threshold (minutes) |
Vault Type & Capacity
{
"storage_details": { "used_size": 40900613898, "drive_size": 58581416960 }
}
drive_size is only meaningful for Private vaults — it's the storage
allotted on customer-owned hardware. Cloud vaults are elastic; a
drive_size on a Cloud vault does not represent a hard ceiling the way it
does on a Private vault.
Connectivity Threshold
axcient_get_vault_threshold
Returns connectivity_threshold — the number of minutes a vault can be
unreachable before Axcient raises a WARNED status on it. This is
vault-level, distinct from a job's own vault_rp_threshold (see the jobs
skill), which governs recovery-point age rather than reachability.
Changing the Threshold
axcient_set_vault_threshold
⚠ HIGH-IMPACT. Raising this threshold delays how quickly a vault connectivity loss surfaces as an alert; lowering it makes the vault more sensitive to brief network blips. This changes what technicians and monitoring integrations see as "healthy," not the underlying data. Confirm the intended value and the business reason (e.g. a site with known intermittent WAN) with the requester before calling this — a threshold set too high silently masks a real outage for longer than expected.
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 · 131 lines · 56 tokens per session scan A 71e08a2513fc
Axcient Vaults is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (52 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 1,192 once invoked, about $0.0002 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.
Axcient Vaults compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| Axcient VaultsWYRE-AI/msp-claude-plugins | Skill | 52 | today | Apache-2.0 | A | 56 | Claude Code |
| rented-server-setupnaveedharri/benai-skills | Skill | 80 | 1mo ago | MIT | A | 258 | Claude Code |
| allow-teamnaveedharri/benai-skills | Skill | 80 | 1mo ago | MIT | A | 181 | Claude Code |
| gcloud-cli-health-checkMSApps-Mobile/claude-plugins | Skill | 11 | today | MIT | A | 175 | Claude Code |
| cloudflare-managerckorhonen/claude-skills | Skill | 26 | 1mo ago | MIT | A | 69 | Claude Code |
| aws-spa-deployziniman/ai-instruct | Skill | 29 | 19d ago | Apache-2.0 | A | 142 | Claude Code |
| dell-idrac-bmc-opsdryvist/claude-code-plugins | Skill | 3 | today | Apache-2.0 | A | 67 | Claude Code |