plugin-review

A security review process for a WordPress plugin, using either its WordPress.org slug, a URL, or the plugin code in the current directory.

In plain words
What is it for?
Use it to review a remote plugin identified by slug or URL, or to inspect a local plugin directory and its main PHP file.
Why use it?
It helps assess whether a plugin is safe to install and produces a recommendation to approve, conditionally approve, or reject it.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/a8cteam51/claude-code-plugins/plugin-review
Any agent
npx skills add a8cteam51/claude-code-plugins --skill plugin-review
Clone the repo
git clone --depth 1 https://github.com/a8cteam51/claude-code-plugins

Made for: Claude Code, Codex.

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,441 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.03441
Opus 5 $0.00009 $0.01721
Sonnet 5 $0.00004 $0.00688
Haiku 4.5 $0.00002 $0.00344

Measured 2d ago against content hash 8e672f8b05d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

plugin-review scanned grade B with 1 finding 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.

The scan reads SKILL.md. This mod also ships 5 executable files (lib/check-deps.sh, lib/fetch-plugin.sh, lib/github-check.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Recursive force deletemediumDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf /tmp/plugin-review-<slug>/

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

plugins/plugin-review/skills/plugin-review/SKILL.md · 308 lines

How it starts

The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.

WordPress Plugin Security Review

You are a WordPress security expert performing an automated plugin review. Your job is to assess whether a plugin is safe to install on a client's site, producing a structured report with an approve/conditional/reject recommendation.

Input Parsing

There are two modes:

Remote mode (slug or URL provided)

  • If given a slug directly (e.g., akismet), use it as-is
  • If given a wordpress.org URL (e.g., https://wordpress.org/plugins/akismet/), extract the slug from the URL path

Local mode (no argument provided)

If no slug or URL is given, assume we're inside a WordPress plugin directory and should review the local code.

  1. Look for the main plugin PHP file in the current working directory. The main file has a Plugin Name: header comment. Use Glob to find *.php in the root of the working directory, then read each until you find the one with the Plugin Name: header.
  2. Extract from that file: Plugin Name, Version, Text Domain (or derive the slug from the directory name).
  3. Set the source directory to the current working directory.
  4. Try to fetch wp.org metadata using the slug — if the plugin is on wordpress.org, you'll get reviews, ratings, install counts, support threads, and CVE data. If it returns a 404, this is likely a private/unreleased plugin — note this and proceed with code-only review.
  5. Do NOT download the plugin zip — you already have the source.
  6. Do NOT clean up the working directory at the end — it's the user's code, not a temp directory.

Set a LOCAL_MODE=true flag to remember to skip download and cleanup steps.

Store the slug in a variable for use in all subsequent steps.

Step 1: Check Dependencies

Determine the directory where this skill's files live. It is the directory containing this skill.md file. Store this as SKILL_DIR.

Run the dependency checker:

bash "$SKILL_DIR/lib/check-deps.sh"

If it reports missing dependencies and the user declines installation, stop and explain what's needed.

Read the full file on GitHub · 308 lines

Files

What ships with it

9 files beside SKILL.md 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.

  1. 2d ago First seen · 308 lines · 18 tokens per session scan B 8e672f8b05d4

Subscribe to this mod's changes

plugin-review is a skill published in the GitHub repository a8cteam51/claude-code-plugins (3 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 3,441 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens