pm-guard

Install

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.

Security

Grade A, and why

pm-guard 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 2d 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.

.claude-plugin/marketplace.json · 27 lines

What it actually says

{
  "name": "pm-guard",
  "owner": {
    "name": "udon!"
  },
  "metadata": {
    "description": "Package manager guard plugin for Claude Code"
  },
  "plugins": [
    {
      "name": "pm-guard",
      "source": "./plugins/pm-guard",
      "description": "Never accidentally npm install in a pnpm project again — guards npm, yarn, pnpm, bun, and deno.",
      "author": {
        "name": "udon!"
      },
      "repository": "https://github.com/udonc/pm-guard",
      "license": "MIT",
      "keywords": [
        "package-manager", "guard", "hooks",
        "npm", "yarn", "pnpm", "bun", "deno",
        "nodejs", "javascript", "typescript"
      ]
    }
  ]
}

Changes

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.

Related

Other plugins, from other repositories