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 skills add Lonsdale201/wp-agent-skills --skill wp-phpcs-coding-standardsgit clone --depth 1 https://github.com/Lonsdale201/wp-agent-skillsWrote 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.
[](https://agentmods.dev/skills/lonsdale201/wp-agent-skills/wp-phpcs-coding-standards)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/wp-phpcs-coding-standards"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wp-phpcs-coding-standards/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.
<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/wp-phpcs-coding-standards"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wp-phpcs-coding-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00261 | $0.02864 |
| Opus 5.5 | $0.00104 | $0.01146 |
| Sonnet 5.5 | $0.00052 | $0.00573 |
| Haiku 4.5 | $0.00026 | $0.00286 |
Grade A, and why
wp-phpcs-coding-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 1mo 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress coding standards with PHPCS
PHP_CodeSniffer (phpcs) checks code against a ruleset; phpcbf auto-fixes what it can. The WordPress Coding Standards (WPCS) are the rulesets; PHPCompatibility flags syntax that breaks on your minimum PHP version. This skill wires them up correctly — the package names and the WPCS 3.x renames are where people get stuck.
When to use this skill
- Adding coding-standards linting to a plugin/theme (or to the
.phpcs.xml.distthe test scaffolder dropped in). - Writing or auditing a
phpcs.xml.distruleset. - Fixing "Referenced sniff … does not exist", "standard not installed", or
allow-pluginserrors. - Migrating a ruleset from WPCS 2.x to 3.x.
Install (exact packages — names are confusing)
composer config --no-plugins allow-plugins.dealerdirect/phpcodesniffer-composer-installer true
composer require --dev \
wp-coding-standards/wpcs:"^3.4.1" \
phpcompatibility/phpcompatibility-wp:"^2.1" \
dealerdirect/phpcodesniffer-composer-installer:"^1.0"
Four things that trip people up, all verified:
squizlabs/php_codesnifferis still the correct Packagist name even though the project moved to thePHPCSStandardsGitHub org. WPCS pulls it in transitively, so you usually don't list it. WPCS 3.4.1 requires PHPCS^3.13.5, not 4.x — don't forcesquizlabs/php_codesniffer:^4.- The installer is still
dealerdirect/phpcodesniffer-composer-installeron Packagist (the repo is nowPHPCSStandards/composer-installer, but the package name is unchanged). It auto-registers WPCS and PHPCompatibility with PHPCS, so you never runphpcs --config-set installed_paths …by hand. - PHPCompatibilityWP: use the stable
^2.1. The README advertises^3.0@dev, but 3.0 is alpha-only; pin^2.1for production unless you deliberately want the alpha. - Do not use WPCS below 3.4.1. Version 3.4.1 fixes arbitrary command execution in
WordPress.WP.EnqueuedResourceParameterswhen scanning untrusted PHP. This affects theWordPressandWordPress-Extrarulesets; update developer machines and CI runners, not only production dependencies.
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.
- 1mo ago First seen · 192 lines · 261 tokens per session scan A 44ee2f8476a2
wp-phpcs-coding-standards is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (24 stars, last pushed 3d ago), licensed MIT. It adds 261 tokens to every session and 2,864 once invoked, about $0.0010 per session on Opus 5.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
php-quality
PHP static analysis, code style and modern idioms for PHP 8.3 to 8.5. Use when setting up phpstan.neon or a baseline, choosing PHPStan or Psalm, PHP-CS-Fixer or PHPCodeSniffer, PER-CS or PSR-12, configuring Rector quality sets, or reviewing PHP for readonly, enums, property hooks and the pipe operator.
wp-coding-standards
Use when setting up PHPCS with WordPress Coding Standards (WPCS), configuring phpcs.xml.dist, running phpcs/phpcbf, fixing sniff violations, adding PHPCS to CI (GitHub Actions), configuring IDE integration, or verifying a plugin meets WP.org code style requirements. Covers squizlabs/phpcodesniffer…
resharper-clt
Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. USE FOR: jb inspectcode; jb cleanupcode; stronger C# inspections, cleanup profiles, and CI-friendly JetBrains analysis. DO NOT USE FOR: replacing tests with inspection output; ad-hoc formatting-only work when the repo intentionally…
roslynator
Use the open-source free Roslynator analyzer packages and optional CLI for .NET. USE FOR: Roslynator.Analyzers setup; Roslynator CLI checks or cleanup; C# linting, static analysis, and code-fix automation. DO NOT USE FOR: overlapping analyzer packs with no consolidation plan; formatting-only work owned by another…
stylecop-analyzers
Use the open-source free StyleCop.Analyzers package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement…
mvc-expert
Expert guidelines to refactor legacy PHP codebases into clean, modern, and scalable MVC-structured projects / Pedoman ahli untuk merefaktor codebase PHP lama menjadi proyek terstruktur MVC yang bersih, modern, dan skalabel.