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.
/plugin marketplace add xonack/wp-php-architecture-claude-skillnpx agentmods add plugins/xonack/wp-php-architecture-claude-skill/wp-php-architecture-claude-skillgit clone --depth 1 https://github.com/xonack/wp-php-architecture-claude-skillWrote 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/plugins/xonack/wp-php-architecture-claude-skill/wp-php-architecture-claude-skill)<a href="https://agentmods.dev/plugins/xonack/wp-php-architecture-claude-skill/wp-php-architecture-claude-skill"><img src="https://agentmods.dev/badge/plugins/xonack/wp-php-architecture-claude-skill/wp-php-architecture-claude-skill.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
wp-php-architecture-claude-skill 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 5d 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.
What it actually says
{
"name": "wp-php-architecture-claude-skill",
"version": "1.0.0",
"description": "Expert WordPress PHP architecture skill covering repository pattern, service layer, DDD adapted for WordPress hooks, SOLID principles in plugin/theme development, and modern PHP patterns for WordPress.",
"skills": [
{
"name": "wp-php-architecture",
"path": "skills/wp-php-architecture/SKILL.md"
}
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 45 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago First seen · 12 lines scan A 2d9d320b2277
wp-php-architecture-claude-skill is a plugin published in the GitHub repository xonack/wp-php-architecture-claude-skill (3 stars, last pushed 7mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
wp-ux-design-claude-skill
WordPress UX/design enforcement skill covering Core Web Vitals, mobile-first design, typography systems, color management, navigation UX, page builder patterns, and loading/error states.
craftcms-claude-skills
Production-ready skills and agents for Craft CMS 5 development. Plugin development (elements, services, controllers, migrations, events, testing, headless, configuration), site development (content modeling, Twig templates, atomic design, multi-site), a name-routed index of 23 plugin references (config, Twig/PHP API…
laravel-spatie-event-sourcing
Design and generate Spatie/Laravel event-sourced domains through a design conversation.
126-java-exception-handling
Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast principles, handling thread interruption…
301-frameworks-spring-boot-core
Use when you need to review, improve, or build Spring Boot 4.0.x applications — including proper usage of @SpringBootApplication, component annotations (@Controller, @Service, @Repository), bean definition and scoping, configuration classes and @ConfigurationProperties (with @Validated), component scanning…
121-java-object-oriented-design
Use when you need to review, improve, or refactor Java code for object-oriented design quality — including applying SOLID, DRY, and YAGNI principles, improving class and interface design, fixing OOP concept misuse (encapsulation, inheritance, polymorphism), identifying and resolving code smells (God Class, Feature…