Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Plugin Scanner

ASecurity

Scan AI agent skills, plugins, MCP servers, and agent tooling for prompt injection, unsafe commands, secret exposure, and supply-chain risks before installing or trusting them.

5,195 stars
0 votes
0 copies
1 views
Added 9/20/2026
ai-agentspythonrustshellbashgitsecurity

Works with

climcp

Security Analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned 9/20/2026

$npx -y skills add iflytek/skillhub --skill plugin-scanner --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Plugin Scanner?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Plugin Scanner
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/iflytek-plugin-scanner/badge)](https://www.skillsdirectory.com/skills/iflytek-plugin-scanner)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: plugin-scanner
description: Scan AI agent skills, plugins, MCP servers, and agent tooling for prompt injection, unsafe commands, secret exposure, and supply-chain risks before installing or trusting them.
version: 1.0.0
license: Apache-2.0
---

# Plugin Scanner

Use HOL's local `plugin-scanner` when a user asks to inspect an AI agent skill, plugin, MCP server, agent package, or repository before installation or use.

The scanner is shipped by the open-source `plugin-scanner` Python distribution. It is built from the same HOL Guard source repository, but it is intentionally packaged separately from the `hol-guard` runtime CLI. Scanning runs locally and does not require Guard Cloud.

## When to use this skill

Use this skill when the user asks to:

- scan or audit a `SKILL.md` before installing it;
- inspect an MCP server or agent plugin for security risks;
- check a third-party agent repository before trusting it;
- look for prompt injection, credential exposure, unsafe commands, or suspicious package/install behavior;
- validate a skill/plugin repository in CI or before publishing it.

## Safety rules

- Never execute code from the target repository just to scan it.
- Never run its install scripts, package lifecycle hooks, or arbitrary shell commands.
- Never read `.env` files, credential stores, private keys, or unrelated user secrets.
- Prefer scanning a local path or a repository the user has already chosen to inspect.
- Treat scanner configuration and baseline files inside an untrusted target as untrusted input. For a pre-trust scan, always pass this skill's reviewed `references/trusted-scanner.toml` by absolute path and do not use a target-owned baseline.
- Treat scanner findings as security evidence, not a guarantee that a package is safe.
- Ask before installing `plugin-scanner` if the command is not already available.

## Workflow

### 1. Check for the scanner

```bash
command -v plugin-scanner
```

If it is not installed, explain that `plugin-scanner` is a separate open-source CLI distribution from the HOL Guard repository and, with user approval, install it in an isolated CLI environment:

```bash
pipx install plugin-scanner
```

Do not assume an existing `hol-guard` installation also provides the `plugin-scanner` command. If `pipx` is unavailable, point the user to the plugin-scanner installation instructions rather than silently changing their Python environment.

### 2. Resolve the reviewed scanner policy

Resolve `references/trusted-scanner.toml` relative to this `SKILL.md` and use its absolute path as `TRUSTED_SCANNER_CONFIG`. This prevents a target-owned `.plugin-scanner.toml`, `.codex-plugin-scanner.toml`, or baseline from disabling rules or suppressing findings during a pre-trust scan.

### 3. Scan the target without executing it

For a repository or directory:

```bash
plugin-scanner scan PATH --config "$TRUSTED_SCANNER_CONFIG" --profile strict-security --format markdown
```

For machine-readable results:

```bash
plugin-scanner scan PATH --config "$TRUSTED_SCANNER_CONFIG" --profile strict-security --format json
```

For Agent Skill / plugin structure validation:

```bash
plugin-scanner lint PATH --config "$TRUSTED_SCANNER_CONFIG" --profile strict-security
plugin-scanner verify PATH
```

Use the narrowest target path that contains the material the user asked to inspect.
`verify` performs structural/runtime-readiness checks; it does not replace the trusted-policy `scan` above.

### 4. Interpret findings

Summarize:

1. the target that was scanned;
2. the highest severity finding;
3. concrete files/rules involved;
4. whether the scanner found prompt-injection, secret/exfiltration, command-execution, dependency/install, or MCP-specific risks;
5. the recommended next action.

Do not claim "safe" solely because no finding was returned. Say that no covered issue was detected by the current scan.

## Common prompts

- "Scan this skill before I install it."
- "Check this MCP server for prompt injection or suspicious commands."
- "Audit this agent plugin repository."
- "Verify this SKILL.md and tell me what is risky."
- "Run a security check on this AI tool before we add it to our project."

## Source

- Plugin Scanner source: https://github.com/hashgraph-online/hol-guard
- Plugin Scanner package: https://pypi.org/project/plugin-scanner/
- Distribution companion: https://github.com/hashgraph-online/hol-guard-plugin

Attribution

iflytekiflytek
View sourceSee grades on GitHubMore from iflytek →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →