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/iwritec0de/wp-dev/wordpress-standardsnpx skills add iwritec0de/wp-dev --skill wordpress-standardsgit clone --depth 1 https://github.com/iwritec0de/wp-devWhat 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.00121 | $0.05663 |
| Opus 5 | $0.00060 | $0.02831 |
| Sonnet 5 | $0.00024 | $0.01133 |
| Haiku 4.5 | $0.00012 | $0.00566 |
Grade A, and why
wordpress-standards 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 yesterday.
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 — 676 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Coding Standards & Conventions
This skill covers WordPress naming conventions, file organization, coding style, and documentation standards as defined by the WordPress Coding Standards (WPCS).
File Naming
| Type | Pattern | Example |
|---|---|---|
| Class file | class-{name}.php |
class-my-plugin-admin.php |
| Interface | interface-{name}.php |
interface-my-plugin-handler.php |
| Trait | trait-{name}.php |
trait-my-plugin-singleton.php |
| Template | template-{name}.php |
template-full-width.php |
| Template part | {section}-{name}.php |
content-single.php |
| Admin page | admin-{page}.php |
admin-settings.php |
| Include | descriptive lowercase | helpers.php, post-types.php |
Function & Hook Naming
All functions, hooks, and global variables must be prefixed with the plugin/theme slug:
// Functions: prefix_action_description — always include return types
function myplugin_register_post_types(): void {}
function myplugin_enqueue_admin_scripts(): void {}
function myplugin_get_option( string $key ): string {}
// Hooks: prefix/action_description
do_action( 'myplugin_after_save', $post_id );
$value = apply_filters( 'myplugin_option_value', $value, $key );
// Classes: Prefix_Descriptive_Name (or namespaced)
class MyPlugin_Admin_Settings {}
// Or with namespaces:
namespace MyPlugin\Admin;
class Settings {}
Naming Conventions
| Element | Convention | Example |
|---|---|---|
| Functions | snake_case with prefix |
myplugin_get_user_data() |
| Classes | Upper_Snake_Case or namespaced |
MyPlugin_Data_Handler |
| Methods | snake_case |
$this->get_items() |
| Constants | UPPER_SNAKE_CASE with prefix |
MYPLUGIN_VERSION |
| Variables | $snake_case |
$user_name |
| Options | prefix_option_name |
myplugin_settings |
| Post meta | _prefix_meta_key (leading _ = hidden) |
_myplugin_custom_field |
| Transients | prefix_cache_key |
myplugin_api_response |
| Nonce actions | prefix_action |
myplugin_save_settings |
| Text domain | match plugin/theme slug | my-plugin |
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.
- yesterday First seen · 676 lines · 121 tokens per session scan A d3be73fc0f39
wordpress-standards is a skill published in the GitHub repository iwritec0de/wp-dev (1 stars, last pushed 4mo ago), licensed MIT. It adds 121 tokens to every session and 5,663 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…