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-scaffoldnpx skills add pluginslab/wp-agentic-kit --skill wordpress-scaffoldgit 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.00109 | $0.01073 |
| Opus 5 | $0.00055 | $0.00536 |
| Sonnet 5 | $0.00022 | $0.00215 |
| Haiku 4.5 | $0.00011 | $0.00107 |
Grade A, and why
wordpress-scaffold 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 Scaffold
Scaffolds a brand-new WordPress plugin through a short interview. Greenfield only — if a *.php file with a Plugin Name: header already exists in the working directory, stop and use the wordpress-feature skill.
Phases
-
Identity. Ask one question at a time, don't continue without a clear answer:
- Plugin name (e.g. "Order Tracker")
- One-sentence description
- Vendor prefix (optional, e.g.
acme) - Slug — derive
acme-order-trackerororder-tracker; confirm - PHP namespace — PascalCase from slug, e.g.
AcmeOrderTracker; confirm
Show the full identifier set before generating: slug, text domain (= slug), namespace, constant prefix, function prefix, options key.
-
Constitution. Write
.claude/plans/constitution.mdfrom the template in @.claude/references/PLANNING.md. The file has two binding levels:- Default sections (loose) —
@wordpress/*packages, Composer deps, deploy lane, quality gates. Accept the template defaults unless the user wants different. - Allowed sections (strict, security-relevant) — sanitize functions, escape functions, capability constants, forbidden constructs. Match @.claude/references/SECURITY.md exactly.
Confirm both before writing. The distinction is the point: treat everything as strict and the agent asks permission for trivia; treat nothing as strict and the plugin is one missing escape from disclosure.
- Default sections (loose) —
-
Feature selection. Ask one at a time: Settings page? REST API? Gutenberg blocks (@.claude/references/BLOCKS.md)? Editor extensions?
-
Spec + plan. Create
.claude/plans/features/000-initial-scaffold/and writespec.md+plan.mddescribing the initial scaffold. This becomes the project's first plan artifact. -
Generate. Standard plugin layout:
{slug}.php(bootstrap with header,*_VERSION/*_PATH/*_URL/*_FILEconstants, singleget_instance()class, top-level activation/deactivation hooks),includes/class-utils.php,includes/class-settings.php(if selected),includes/api/class-rest.php+class-rest-example.php(if selected),src/blocks/test-block/(if selected),src/extensions/(if selected),languages/,package.json(if blocks/extensions),composer.json,phpcs.xml.dist,readme.txt,uninstall.php,.gitignore. Every PHP file MUST start with theABSPATHguard.
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 · 109 tokens per session scan A 891ce982305d
wordpress-scaffold is a skill published in the GitHub repository pluginslab/wp-agentic-kit (18 stars, last pushed 2mo ago), licensed MIT. It adds 109 tokens to every session and 1,073 once invoked, about $0.0005 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.