What is wp-spec-to-goal?

A workflow that turns a rough WordPress plugin or feature idea into GOAL.md, VERIFY.md, and PROGRESS.md files for Codex. These files describe the desired result, how to test it, and the work history.

Use it to prepare WordPress work for autonomous implementation, optionally create missing project files, and define verification with wp-env, Playwright, and wp-eval.

It removes the manual effort of turning an incomplete idea into a structured implementation task with browser and WordPress checks.

wp-spec-to-goal — Skill for Claude Code by nathanonn

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 nathanonn/agent-skills --skill wp-spec-to-goal

Clone the repo

git clone --depth 1 https://github.com/nathanonn/agent-skills

Made for: Claude Code.

Or install wp-spec-to-goal, the plugin that ships this one along with the rest of its 1 skill.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nathanonn/agent-skills/wp-spec-to-goal/github.svg)](https://agentmods.dev/skills/nathanonn/agent-skills/wp-spec-to-goal)

Your own site

<a href="https://agentmods.dev/skills/nathanonn/agent-skills/wp-spec-to-goal"><img src="https://agentmods.dev/badge/skills/nathanonn/agent-skills/wp-spec-to-goal/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nathanonn/agent-skills/wp-spec-to-goal"><img src="https://agentmods.dev/badge/skills/nathanonn/agent-skills/wp-spec-to-goal.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 4,119 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 4 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Agent Snooping · line 54
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
medium MCP Rug Pull · line 148
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]
medium MCP Rug Pull · line 156
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]
medium MCP Rug Pull · line 157
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00128	$0.04119
Opus 5	$0.00064	$0.02060
Sonnet 5	$0.00026	$0.00824
Haiku 4.5	$0.00013	$0.00412

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

Security

Grade A, and why

wp-spec-to-goal 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 11d 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.

plugins/wp-spec-to-goal/skills/wp-spec-to-goal/SKILL.md · 217 lines

How it starts

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

wp-spec-to-goal — Vague WP Plugin Idea → Codex /goal Bundle

Turn a rough WordPress plugin or feature idea into the three files Codex /goal needs to drive autonomous implementation:

goals/<slug>/
  GOAL.md       what done looks like (full WP plugin template)
  VERIFY.md     how /goal proves it's done (wp-env + playwright-cli + wp-eval, folded in)
  PROGRESS.md   the audit trail /goal will populate

The skill optionally scaffolds a missing plugin (plugin folder + .wp-env.json + package.json + AGENTS.md) and prints a tailored /goal command at the end.

Prerequisite — playwright-cli. The generated VERIFY.md drives browser-visible checks through playwright-cli. Install it once on the machine that runs /goal: npm install -g @playwright/cli@latest then playwright-cli install --skills (needs Node.js 18+). If it isn't installed, this skill still produces the bundle — it just prepends a "Setup prerequisites" section to VERIFY.md so /goal knows to install it first.

Why this skill exists

A full multi-prompt workflow kit is overkill for plugins or features that fit in one or two goal slices. This skill collapses the "spec → goal trio" hop into a single guided conversation that:

batches clarifying questions (so the user makes 2-3 decisions per round, not 20)
recommends a default for every choice (so they can move fast when the recommendation looks right)
bakes in the standard stack: wp-env + playwright-cli + wp-eval
writes the same template shapes already validated in their templates kit (full WordPress GOAL.md / VERIFY.md)

It does not replace the multi-prompt kit when shipping a complex plugin from a long requirements doc. Use the kit for big builds; use this skill for the small-to-medium ones — and "small to medium" is genuinely small to medium, not just trivially simple.

Core flow

Probe the project — inspect the cwd to learn what's already in place.
Decide single goal vs. multi-goal — judge complexity from the spec; if multi-shaped, offer to split via goals-plan.md.
Ask in focused batches — 2-4 questions per round, each with options + recommendation + reasoning, until 95% confident.
Optionally scaffold — if the project is missing pieces and the user agrees, create only what they confirm.
Write the goal trio — GOAL.md + VERIFY.md (with wp-env / playwright-cli / wp-eval folded in) + initial PROGRESS.md, at goals/<slug>/.
Hand off — print the file paths + a tailored /goal command + a short "how to run" note.

Read the full file on GitHub · 217 lines

Files

What ships with it

4 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.

11d ago First seen · 217 lines · 128 tokens per session scan A df340ffaf10b

Subscribe to this mod's changes

wp-spec-to-goal is a skill published in the GitHub repository nathanonn/agent-skills (19 stars, last pushed 23d ago), licensed MIT. It adds 128 tokens to every session and 4,119 once invoked, about $0.0006 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-30.

Planning Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

wp-spec-to-goal