claude-code-plugin

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

claude-code-plugin 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 3d 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-code-plugin/.claude-plugin/plugin.json · 12 lines

What it actually says

{
  "name": "mcp-scanner",
  "description": "Security scanning for MCP servers using YARA rules, LLM analysis, and Cisco AI Defense. Detect prompt injection, tool poisoning, and other threats in MCP tools, prompts, and resources.",
  "version": "1.0.0",
  "author": {
    "name": "Cisco AI Defense"
  },
  "repository": "https://github.com/cisco-ai-defense/mcp-scanner",
  "license": "Apache-2.0",
  "keywords": ["security", "mcp", "scanning", "yara", "threat-detection"]
}

Files

What ships with it

1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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