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/MSApps-Mobile/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/msapps-mobile/claude-plugins/session-backup)<a href="https://agentmods.dev/plugins/msapps-mobile/claude-plugins/session-backup"><img src="https://agentmods.dev/badge/plugins/msapps-mobile/claude-plugins/session-backup/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/plugins/msapps-mobile/claude-plugins/session-backup"><img src="https://agentmods.dev/badge/plugins/msapps-mobile/claude-plugins/session-backup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
session-backup 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 1mo 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": "session-backup",
"version": "0.4.0",
"description": "Automated daily backups of Cowork skills, scheduled tasks, plugins, and configs to Google Drive. Supports multi-account merge and split uploads for large backups.",
"author": {
"name": "MSApps",
"url": "https://msapps.mobi"
},
"license": "MIT",
"privacy_policy": "https://opsagents.agency/privacy",
"terms_of_service": "https://opsagents.agency/terms",
"keywords": [
"backup",
"session",
"skills",
"google-drive",
"automation",
"scheduled",
"cowork",
"sosa-agents"
],
"platforms": [
"claude-code",
"cowork"
],
"sosa": {
"compliant": true,
"level": 2,
"impact": "medium",
"methodology": "https://github.com/MSApps-Mobile/claude-plugins/blob/main/docs/SOSA.md",
"whitepaper": "https://github.com/MSApps-Mobile/claude-plugins/blob/main/docs/sosa-whitepaper.pdf",
"pillars": {
"supervised": "User triggers or approves scheduled backups",
"orchestrated": "Collect \u2192 compress \u2192 upload pipeline with Google Drive",
"secured": "Uses google-drive-upload config, no additional credentials",
"agents": "R=session-backup, T=Google-Drive+local-fs, M=backup-manifest, P=collect-compress-upload-verify"
}
},
"topics": [
"sosa-agents"
]
}
What it installs
The manifest is a name and a version. 1 skill, 3 commands travel with it, and installing the plugin installs all of them — 71 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.
- 1mo ago First seen · 43 lines scan A 229f30fab1d3
session-backup is a plugin published in the GitHub repository MSApps-Mobile/claude-plugins (9 stars, last pushed today), licensed MIT. 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-13.
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.
azure-mcp
Claude plugins for the Azure MCP Server — read-only Azure observability, cost, and resource health in natural language: Monitor metrics and Log Analytics KQL, retail pricing, quotas, Advisor recommendations, Resource Health, AppLens diagnostics, and subscription/resource-group inventory across tenants.
cloudops-pack
Cross-vendor network and cloud infrastructure operations — device/network health, capacity planning, and cost management across whatever network monitoring (Auvik, Meraki, Domotz) and cloud platforms (Azure, DigitalOcean) you have connected.
axcient
Claude plugins for Axcient x360Recover - clients, devices, backup jobs, vaults, and appliances for BCDR operations.
homelab-ops
Operational runbooks for infrastructure state, maintenance, and recovery: monitoring-first checks, Proxmox VE cluster operations, DNS ingress convergence, secrets-engine identity bring-up, Terrakube operations, PXE netboot installs, LLM router operations, workstation off-box backup, Dell iDRAC BMC operations, and…
infra-orchestration
Cross-repo infrastructure orchestration for Terraform and Ansible workflows.