wp-project-triage

wp-project-triage is a skill for Claude Code from morrealev/wordpress-manager. It costs 50 tokens per session (370 once invoked), scanned A, original, no licence file.

A guide for inspecting a WordPress code repository, such as a plugin, theme, block theme, WordPress core, or complete site. It produces a structured JSON report about the project and its tooling, tests, and version clues.

In plain words
What is it for?
Use it to identify what a WordPress project contains, discover available tests and tools, infer version information, and set workflow safeguards.
Why use it?
It gives you a consistent starting assessment before making changes or choosing a development workflow.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the wordpress-manager plugin — 46 skills, 5 commands, 12 agents, 1 hook, 2 MCP servers shipped together

Good fit Use it to identify what a WordPress project contains, discover available tests…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/morrealev/wordpress-manager/wp-project-triage
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 morrealev/wordpress-manager --skill wp-project-triage
Clone the repo
git clone --depth 1 https://github.com/morrealev/wordpress-manager

Made for: Claude Code.

Or install wordpress-manager, the plugin that ships this one along with the rest of its 46 skills, 5 commands, 12 agents, 1 hook, 2 MCP servers.

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-project-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/morrealev/wordpress-manager/wp-project-triage.svg)](https://agentmods.dev/skills/morrealev/wordpress-manager/wp-project-triage)
Your own site
<a href="https://agentmods.dev/skills/morrealev/wordpress-manager/wp-project-triage"><img src="https://agentmods.dev/badge/skills/morrealev/wordpress-manager/wp-project-triage.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 370 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.00050 $0.00370
Opus 5 $0.00025 $0.00185
Sonnet 5 $0.00010 $0.00074
Haiku 4.5 $0.00005 $0.00037

Measured 6d ago against content hash 628c3834e4f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

wp-project-triage 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 6d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/detect_wp_project.mjs), 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/wp-project-triage/SKILL.md · 41 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Files

What ships with it

2 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. 6d ago First seen · 41 lines · 50 tokens per session scan A 628c3834e4f7

Subscribe to this mod's changes

wp-project-triage is a skill published in the GitHub repository morrealev/wordpress-manager (8 stars, last pushed 6mo ago), with no licence file. It adds 50 tokens to every session and 370 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. 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

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens