wp-plugin-audit

wp-plugin-audit is a skill for Claude Code from mralaminahamed/wp-dev-skills. It costs 297 tokens per session (3,188 once invoked), scanned B, original, MIT.

A read-only review of a WordPress plugin's versions, metadata, naming, translations, documentation, code conventions, and security. It compares related files and checks each possible issue against the actual code before reporting it.

In plain words
What is it for?
Use it before a release or after a major refactor to check metadata, prefixes, internationalisation, documentation, coding practices, and security-related problems with file and line references.
Why use it?
It finds inconsistencies caused by refactoring or release changes while reducing false alarms and preserving the plugin's files.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md.

Part of the wp-dev-skills plugin — 19 skills, 1 command shipped together

Good fit Use it before a release or after a major refactor to check metadata, prefixes, internationalisation, documentation, coding practices, and security-related problems with file and line references.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mralaminahamed/wp-dev-skills/wp-plugin-audit
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.

Any agent
npx skills add mralaminahamed/wp-dev-skills --skill wp-plugin-audit
Clone the repo
git clone --depth 1 https://github.com/mralaminahamed/wp-dev-skills

Made for: Claude Code.

Or install wp-dev-skills, the plugin that ships this one along with the rest of its 19 skills, 1 command.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for wp-plugin-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/mralaminahamed/wp-dev-skills/wp-plugin-audit/github.svg)](https://agentmods.dev/skills/mralaminahamed/wp-dev-skills/wp-plugin-audit)
Your own site
<a href="https://agentmods.dev/skills/mralaminahamed/wp-dev-skills/wp-plugin-audit"><img src="https://agentmods.dev/badge/skills/mralaminahamed/wp-dev-skills/wp-plugin-audit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for wp-plugin-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/mralaminahamed/wp-dev-skills/wp-plugin-audit"><img src="https://agentmods.dev/badge/skills/mralaminahamed/wp-dev-skills/wp-plugin-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 297 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,188 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00297 $0.03188
Opus 5 $0.00148 $0.01594
Sonnet 5 $0.00059 $0.00638
Haiku 4.5 $0.00030 $0.00319

Measured 9d ago against content hash 97b23cb1e815, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

wp-plugin-audit 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 9d 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.

Cloud metadata endpointmediumServer-side request forgery

One request to 169.254.169.254 can return temporary IAM credentials.

- **SSRF** — `wp_remote_*`/cURL/`file_get_contents` on a user-supplied URL without `wp_safe_remote_*` + host allowlist + `redirection => 0` (can reach cloud metadata `169.254.169.254` / internal services).

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

skills/wp-plugin-audit/SKILL.md · 127 lines

How it starts

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

WordPress Plugin Consistency Audit

Read-only audit that surfaces inconsistencies across a WP plugin's code, config, and docs. Optimised for recall with low false-positive rate: every candidate is verified against the actual code before it reaches the report.

When to use

  • "Audit the plugin", "find inconsistencies", "consistency/quality sweep".
  • Before a release, or after a large refactor, to catch drift.

Not for: PHPStan type checking or baseline generation — use wp-phpstan (official). WP.org pre-submission review (17 rejection patterns) — use wp-org-submission which has that checklist.

Method

1. Fan out — 4 independent dimensions (parallel agents)

Dispatch one read-only agent per dimension (Explore type, model: haiku), in a single message so they run concurrently. Each returns findings with file:line, the inconsistent value, and the expected/canonical form.

Model note: Dimension agents are pure grep/read with no synthesis — haiku is faster and cheaper. The main thread (whatever model the user has active) does all verification and reporting.

  • A — Version & metadata. Cross-reference every version/metadata source: plugin header (Version, Requires at least, Requires PHP, Tested up to, Text Domain), the version constant, readme.txt (Stable tag + Changelog + Upgrade Notice), composer.json, the .pot Project-Id-Version, and the schema/DB version. Flag every mismatch; note fields that are intentionally independent (schema $db_version ≠ plugin version) so they aren't flagged.

    Also audit the main plugin file header format against the canonical PHPDoc DocBlock style (preferred over plain block comment):

    /**
     * Plugin Name
     *
     * @package           PluginPackage
     * @author            Your Name
     * @copyright         2024 Your Name or Company Name
     * @license           GPL-2.0-or-later
     *
     * @wordpress-plugin
     * Plugin Name:       Plugin Name
     * Plugin URI:        https://example.com/plugin-name
     * Description:       Description of the plugin.
     * Version:           1.0.0
     * Requires at least: 6.5
     * Requires PHP:      7.4
     * Author:            Your Name
     * Author URI:        https://example.com
     * Text Domain:       plugin-slug
     * License:           GPL v2 or later
     * License URI:       http://www.gnu.org/licenses/gpl-2.0.txt
     * Update URI:        https://example.com/my-plugin/
     * Requires Plugins:  my-plugin, yet-another-plugin
     */
    

    Flag: missing @wordpress-plugin marker (distinguishes WP header from plain PHPDoc); missing @package/@author/@copyright/@license PHPDoc fields; Description over 140 characters; License slug not matching License URI; missing Text Domain when plugin has translated strings (requires Dimension B __() detection to confirm strings exist); using a plain /* */ block instead of /** */ PHPDoc block.

Read the full file on GitHub · 127 lines

Files

What ships with it

8 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. 9d ago First seen · 127 lines · 297 tokens per session scan B 97b23cb1e815

Subscribe to this mod's changes

wp-plugin-audit is a skill published in the GitHub repository mralaminahamed/wp-dev-skills (27 stars, last pushed 1mo ago), licensed MIT. It adds 297 tokens to every session and 3,188 once invoked, about $0.0015 per session on Opus 5. A static security scan graded it B with 1 finding (cloud metadata endpoint). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

doctor

Run a read-only hygiene + documentation audit on the current repo. TRIGGER when the user says "is this repo healthy", "check hygiene", "audit this repo" (when they mean inspect, not remediate), "what's drifted", "run doctor", "run a health check", "audit docs", "check for doc drift", "what's broken in this project"…

thettwe/nyann · 152 tokens

wp-performance-review

WordPress performance code review and optimization analysis. Use when reviewing WordPress PHP code for performance issues, auditing themes/plugins for scalability, optimizing WPQuery, analyzing caching strategies, checking code before launch, or detecting anti-patterns, or when user mentions "performance review"…

elvismdev/claude-wordpress-skills · 122 tokens

github-pr-workflow

Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.

paperclipai/paperclip · 39 tokens

issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…

jeremylongshore/tons-of-skills-marketplace · 115 tokens

review-work

Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.

code-yeongyu/oh-my-openagent · 63 tokens

one-way-door

Flags irreversible decisions before commit. Use for data models, infra, auth boundaries, API contracts, event schemas, CI/CD.

jamditis/claude-skills-journalism · 29 tokens