wordpress-coding-standards-php

The official WordPress coding standards for PHP, the programming language commonly used to build WordPress sites and plugins.

In plain words
What is it for?
Use it when writing or reviewing WordPress PHP code.
Why use it?
It helps keep PHP code consistent with WordPress conventions, making it easier to read and maintain.

Cursor rule

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.

agentmods
npx agentmods add rules/automattic/cursor-rules/wordpress-coding-standards-php
Clone the repo
git clone --depth 1 https://github.com/Automattic/cursor-rules
Per session 674 This file is loaded in full into every session.
When invoked 674 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00674 $0.00674
Opus 5 $0.00337 $0.00337
Sonnet 5 $0.00135 $0.00135
Haiku 4.5 $0.00067 $0.00067

Measured 2d ago against content hash 3e114f6d11c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

wordpress-coding-standards-php 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.

wordpress-coding-standards/wordpress-coding-standards-php.mdc · 72 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 72 lines · 674 tokens per session scan A 3e114f6d11c8

Subscribe to this mod's changes

wordpress-coding-standards-php is a cursor rule published in the GitHub repository Automattic/cursor-rules (6 stars, last pushed 1y ago), with no licence file. It adds 674 tokens to every session, about $0.0034 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.