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.
npx agentmods add skills/pluginslab/wp-agentic-kit/wordpress-featurenpx skills add pluginslab/wp-agentic-kit --skill wordpress-featuregit clone --depth 1 https://github.com/pluginslab/wp-agentic-kitWhat 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 | $0.00128 | $0.01066 |
| Opus 5 | $0.00064 | $0.00533 |
| Sonnet 5 | $0.00026 | $0.00213 |
| Haiku 4.5 | $0.00013 | $0.00107 |
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 2d 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.
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
- 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. - Spec. Allocate
.claude/plans/features/NNN-feature-slug/(next zero-padded number). Writespec.mdfrom the template in @.claude/references/PLANNING.md. End with an explicitOut of scopesection. - Plan. Write
plan.mdfrom 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. - Freeze decision. Read the assessment's recommendation:
- freeze (any box checked): run
./scripts/open-plan-pr.sh NNN-slug, dispatch theplan-reviewersub-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, commitspec.md+plan.mdas the first commit, surface the assessment to the user, start step 5. - The user can override either direction.
- freeze (any box checked): run
- Implement. After the plan PR merges (or immediately for "proceed"), mirror open plan steps into the harness task tool (e.g.
TaskCreateif available). Tick off as you go; append toprogress.md. - Findings (lazy). When an MCP lookup (
wp-devdocs,wp-blockmarkup) surfaces a non-obvious fact that shaped the code, append tofindings.md. Skip if nothing surprised you. - Ship. Run
./scripts/quality.sh. Open the feature PR. Dispatchsecurity-revieweron the diff. After merge, archive the feature dir to.claude/plans/archive/{YYYY-MM-DD}-{slug}/.
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.
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.
- 2d ago First seen · 55 lines · 128 tokens per session scan A c656e3a26100
wordpress-feature is a skill published in the GitHub repository pluginslab/wp-agentic-kit (18 stars, last pushed 2mo ago), licensed MIT. It adds 128 tokens to every session and 1,066 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.
Other skills, from other repositories
verify-pr
This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr ", "深度验证这个 PR", A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates — producing tmp/pr -verify- /report.md plus a machine-readable verdict. Designed for the token-free CI…
cua-driver
Drive a native GUI app (macOS, Windows, Linux) via the Qwen Cua Driver CLI (default) or MCP server; snapshot its accessibility tree, act through snapshot-bound element tokens, native menu paths, exact window geometry, or pixel coordinates, and verify from fresh state. Use when the user asks you to operate, drive…
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
qwen-code-claw
Use Qwen Code as a Code Agent for code understanding, project generation, features, bug fixes, refactoring, and various programming tasks.