wordpress-feature

wordpress-feature is a skill for Claude Code from pluginslab/wp-agentic-kit. It costs 128 tokens per session (1,110 once invoked), scanned A, original, MIT.

A planning workflow for adding features or making small maintenance changes to an existing WordPress plugin.

In plain words
What is it for?
Use it for Gutenberg blocks, REST endpoints, settings pages, editor extensions, custom post types, taxonomies, command-line features, and small fixes.
Why use it?
It turns larger plugin changes into a written specification and implementation plan, making the intended work easier to review before coding.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; mentions subagents.

Good fit Use it for Gutenberg blocks, REST endpoints, settings pages, editor extensions, custom post types, taxonomies, command-line features, and small fixes.

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

Made for: Claude Code.

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 wordpress-feature

README.md
[![agentmods](https://agentmods.dev/badge/skills/pluginslab/wp-agentic-kit/wordpress-feature/github.svg)](https://agentmods.dev/skills/pluginslab/wp-agentic-kit/wordpress-feature)
Your own site
<a href="https://agentmods.dev/skills/pluginslab/wp-agentic-kit/wordpress-feature"><img src="https://agentmods.dev/badge/skills/pluginslab/wp-agentic-kit/wordpress-feature/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 wordpress-feature

Your own site · 80×15
<a href="https://agentmods.dev/skills/pluginslab/wp-agentic-kit/wordpress-feature"><img src="https://agentmods.dev/badge/skills/pluginslab/wp-agentic-kit/wordpress-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 128 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,110 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 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.00128 $0.01110
Opus 5.5 $0.00051 $0.00444
Sonnet 5.5 $0.00026 $0.00222
Haiku 4.5 $0.00013 $0.00111

Measured 1mo ago against content hash e6a7c156832d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wordpress-feature 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 1mo 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.

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.

.claude/skills/wordpress-feature/SKILL.md · 55 lines

How it starts

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

WordPress Feature

Adds features (block, REST, settings, extension, CPT, taxonomy, CLI command) and maintenance edits (typos, version bumps) to an existing WordPress plugin. If no main plugin file (*.php with a Plugin Name: header) is present, stop and use the wordpress-scaffold skill.

Mode

Decide first: feature (gets spec + plan, possibly its own PR) or maintenance (typo / version bump / micro-fix; one-line log). Ask if unsure.

Feature mode

  1. Context. Find the main plugin file. Read its constants, namespace, text domain — match the existing conventions exactly. Read .claude/plans/constitution.md; offer to backfill from the codebase if missing.
  2. Spec. Allocate .claude/plans/features/NNN-feature-slug/ (next zero-padded number). Write spec.md from the template in @.claude/references/PLANNING.md. End with an explicit Out of scope section.
  3. Plan. Write plan.md from the same template. Phased steps, file paths in every step, tests encouraged before each implementation step. Fill the Freeze assessment checklist honestly at the end.
  4. Freeze decision. Read the assessment's recommendation:
    • freeze (any box checked): run ./scripts/open-plan-pr.sh NNN-slug, dispatch the plan-reviewer sub-agent against the PR, stop and wait for the human-merged plan PR before starting step 5.
    • proceed (no boxes checked): create feat/NNN-slug, commit spec.md + plan.md as the first commit, surface the assessment to the user, start step 5.
    • The user can override either direction.
  5. Implement. After the plan PR merges (or immediately for "proceed"), mirror open plan steps into the harness task tool (e.g. TaskCreate if available). Tick off as you go; append to progress.md.
  6. Findings (lazy). When an MCP lookup (wp-devdocs, wp-blockmarkup) surfaces a non-obvious fact that shaped the code, append to findings.md. Skip if nothing surprised you.
  7. Ship. Run ./scripts/quality.sh. Open the feature PR. Dispatch security-reviewer and playground-verifier on the diff — in one message so they run concurrently; they don't depend on each other. quality.sh proves the code is well-formed; playground-verifier proves it runs. After merge, archive the feature dir to .claude/plans/archive/{YYYY-MM-DD}-{slug}/.

Read the full file on GitHub · 55 lines

Files

What ships with it

1 file 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. 1mo ago Changed e6a7c156832d
  2. 2mo ago First seen · 55 lines · 128 tokens per session scan A c656e3a26100

Subscribe to this mod's changes

wordpress-feature is a skill published in the GitHub repository pluginslab/wp-agentic-kit (20 stars, last pushed 1mo ago), licensed MIT. It adds 128 tokens to every session and 1,110 once invoked, about $0.0005 per session on Opus 5.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-30.

Related

wordpress-feature compared with skills from other repositories

wordpress-feature next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
wordpress-featurepluginslab/wp-agentic-kitSkill201mo agoMITA128Claude Code
cua-driverQwenLM/qwen-codeSkill30kyesterdayApache-2.0A88Claude Code, Codex
autofix-prQwenLM/qwen-codeSkill30kyesterdayApache-2.0A141Claude Code
codegraphQwenLM/qwen-codeSkill30kyesterdayApache-2.0A0Claude Code, Codex
workflow-authoringQwenLM/qwen-codeSkill30kyesterdayApache-2.0A60Claude Code, Codex
goal-draftQwenLM/qwen-codeSkill30kyesterdayApache-2.0A114Claude Code
stuckQwenLM/qwen-codeSkill30kyesterdayApache-2.0A57Claude Code