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/plugins/wyre-ai/msp-claude-plugins/axcient)<a href="https://agentmods.dev/plugins/wyre-ai/msp-claude-plugins/axcient"><img src="https://agentmods.dev/badge/plugins/wyre-ai/msp-claude-plugins/axcient.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
axcient 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 4d 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.
What it actually says
{
"name": "axcient",
"version": "0.1.1",
"description": "Claude plugins for Axcient x360Recover - clients, devices, backup jobs, vaults, and appliances for BCDR operations",
"author": {
"name": "MSP Claude Plugins Community"
},
"homepage": "https://github.com/wyre-technology/msp-claude-plugins",
"repository": "https://github.com/wyre-technology/msp-claude-plugins",
"license": "Apache-2.0"
}
What it installs
The manifest is a name and a version. 4 skills, 2 commands travel with it, and installing the plugin installs all of them — 208 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 4d ago First seen · 12 lines scan A e7476a0a3d94
axcient is a plugin published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
local-ai
From nothing to a working AI setup you own. Scans the machine for models that fit, installs and wires up the right app with consent at every download, shares it over a private URL, and rents a cloud GPU when a model is too big. Needs shell access.
gcloud-cli-health-check
Google Cloud CLI health check — verifies gcloud is installed, authenticated with the expected account, correct project + region are active, critical APIs are enabled, billing is linked, and Cloud Run services are live across primary + secondary projects. Produces a structured ✅/⚠️/❌ report. Runs via Desktop Commander…
homelab-ops
High-level operational runbooks for homelab management: DR-node power management, DNS ingress convergence, secrets-engine identity bring-up, Proxmox VE cluster operations, Terrakube operations, PXE netboot installs, LLM router operations, workstation off-box backup, Dell iDRAC BMC operations, and resumable ZFS…
infra-orchestration
Cross-repo infrastructure orchestration for Terraform and Ansible workflows.
infra-standards
Infrastructure standards for Proxmox, Terraform, Ansible: VMID/IP assignment ranges and the Terraform-to-Ansible inventory contract.
frontend-architect
Frontend stack expert for Cloudflare deployment, shadcn/ui components, and internal tools architecture. Guides technology choices, deployment patterns, and design system integration.