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.
/plugin marketplace add cwakim/claude-pluginsnpx agentmods add plugins/cwakim/claude-plugins/memory-backupgit clone --depth 1 https://github.com/cwakim/claude-pluginsGrade A, and why
memory-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 yesterday.
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.
This is a copy
92% identical to cwakim-plugins — 37 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "memory-backup",
"description": "Back up Claude Code's machine-local state (/backup): mirror every per-project memory store, handoff note (live and archived), plan document, and the hand-written global config to a private GitHub repo, one squash-merged PR per run. Repo visibility verified before every push, refused if public; every mirrored file secret-scanned before commit (interactive runs ask, cron redacts and flags loudly), credentials never leave the machine. Diff-aware restore fills empty targets wholesale and asks per conflicting file, from GitHub or from a zip, confirming the plan before anything is applied (--dry-run previews the plan and touches nothing). merge converges any number of machines' memories, handoffs, and plans (one, several, or all other mirrors per run) with the same temperament plus keep-both conflict resolution, cross-machine path reconciliation, and union-rebuilt indexes; interactive-only. zip <path> exports the same mirror as a portable dated archive with no GitHub required, asking each run whether to secret-scan first. Optional schedule for the backup (cron, or launchd on macOS so runs missed while asleep fire on wake), cadence is your call (weekly default). An optional S3-compatible object-storage target (AWS S3, GCS, Alibaba OSS, or a self-hosted MinIO) can back up the same tree to a bucket alongside or instead of GitHub: setup creates and hardens the bucket (versioning on, refuses a public bucket), backup mirrors with delete-propagation and the same secret scan, and restore and merge read a bucket the same way they read the repo; both targets can be configured at once, and one /backup run pushes to each.",
"version": "1.2.1",
"author": {
"name": "Charbel Wakim",
"email": "[email protected]"
}
}
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.
- yesterday First seen · 10 lines scan A 60ce06fad67c
memory-backup is a plugin published in the GitHub repository cwakim/claude-plugins (2 stars, last pushed 11d ago), 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. It is 92% identical to cwakim-plugins, differing in 37 lines, and is treated as a copy.
Other plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.