Claude-Booster

Plugin Auditor — Security skill for Claude Code

Security community

Statically audit a Claude Code plugin bundle for dangerous or injected components (hooks, bin/, monitors, workflows, scripts, skill/command/agent injection, manifest provenance) before enabling it — a.

How to install Plugin Auditor

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Claude-Booster/plugin-auditor and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Plugin Auditor does

Statically audit a Claude Code plugin bundle for dangerous or injected components (hooks, bin/, monitors, workflows, scripts, skill/command/agent injection, manifest provenance) before enabling it — a self-contained Claude Code skill.

Alternatives in Security

  • Agentseal — Security toolkit for AI agents 344 ★
  • Openclaw Ops — OpenClaw operations skill with health checks, repair scripts, watchdogs, update triage, and security scans 225 ★
  • Claude Skill Antivirus — Security scanner for Claude Code Skills — 9 engines detect malicious patterns, data exfiltration, dangerous op 64 ★

README

plugin-auditor — see what a plugin runs and loads before you enable it

Python 3.10+ No dependencies Read-only Delegates MCP to mcp-auditor


What it is

A Claude Code **plugin is a filesystem bundle**, not a single MCP server — and when you enable it, many of its parts **execute** (hooks, `bin/` binaries, background monitors, `workflows/*.js`, LSP servers, bundled scripts) or **load into the model's context** (the markdown of its skills, commands, and agents). Reviewing the plugin's *code* misses most of this.

**plugin-auditor** statically inspects a plugin bundle and flags the risky parts in plain English. It is **read-only**: it never runs any hook, script, binary, workflow, monitor, or MCP server from the plugin, and never prints secret values (key names only).

It sits alongside the sibling tools: **config-guard** gates/quarantines untrusted config; **plugin-auditor** deep-analyzes a plugin bundle; **mcp-auditor** audits the MCP tool metadata within it — plugin-auditor delegates to it.

What it inspects

Surfaces inspected: hooks, bin, monitors, workflows and lsp, bundled scripts, skills/commands/agents, manifest, and bundled MCP

  • Hooks — commands that auto-run on Claude events (flags curl|sh, credential reads).
  • bin/ — executables placed on the Bash tool's PATH (Claude can run them