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 yojahny55/claude-wp-builder --skill wp-theme-standardsgit clone --depth 1 https://github.com/yojahny55/claude-wp-builderWrote 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/yojahny55/claude-wp-builder/wp-theme-standards)<a href="https://agentmods.dev/skills/yojahny55/claude-wp-builder/wp-theme-standards"><img src="https://agentmods.dev/badge/skills/yojahny55/claude-wp-builder/wp-theme-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/yojahny55/claude-wp-builder/wp-theme-standards"><img src="https://agentmods.dev/badge/skills/yojahny55/claude-wp-builder/wp-theme-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.00025 | $0.06273 |
| Opus 5 | $0.00013 | $0.03136 |
| Sonnet 5 | $0.00005 | $0.01255 |
| Haiku 4.5 | $0.00003 | $0.00627 |
Grade A, and why
wp-theme-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 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.
How it starts
The opening of the file, as written. The whole thing — 720 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Legacy Theme Standards
This skill defines the mandatory standards for building WordPress themes using the legacy (classic) theme architecture. No block themes, no Full Site Editing (FSE), no theme.json.
Required Theme Files
Every theme MUST include these files:
| File | Purpose |
|---|---|
style.css |
Theme declaration with required headers |
index.php |
Fallback template (required by WordPress) |
functions.php |
Theme setup, hooks, enqueuing, helpers |
screenshot.png |
Theme thumbnail (1200x900px recommended) |
style.css Headers
The style.css file MUST begin with the theme declaration comment. This is how WordPress identifies the theme.
/*
Theme Name: Starter Theme
Theme URI: https://example.com
Author: Developer Name
Author URI: https://example.com
Description: A custom legacy WordPress theme.
Version: 1.0.0
License: GNU General Public License v2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Text Domain: starter
*/
Note: Do not put actual styles in
style.css. Use it only for the header declaration. All styles go inassets/css/styles.css(or similar), enqueued viafunctions.php.
Theme Directory Structure
theme-name/
├── assets/
│ ├── css/
│ │ └── styles.css # Main design system stylesheet
│ ├── js/
│ │ └── main.js # Main client-side JS
│ └── images/ # Theme images (logo fallback, icons, etc.)
├── inc/
│ ├── theme-setup.php # Theme supports, nav menus, content width
│ ├── i18n.php # Internationalization helpers (if bilingual)
│ └── performance.php # WebP delivery + prefix_image() right-size helper
├── fields/ # SCF/ACF field definitions — one file per group
│ ├── hero.php # BARE acf_add_local_field_group() calls (seed only)
│ ├── settings.php
│ └── ...
├── acf-json/ # SCF/ACF Local JSON — the field SOURCE OF TRUTH
│ ├── group_hero.json # auto-written from fields/*.php on first load,
│ └── ... # dashboard-editable, edits sync back here
├── template-parts/
│ ├── section-hero.php # Reusable section templates
│ ├── section-services.php
│ └── ...
├── functions.php # Main functions file (requires inc/ files)
├── header.php # Site header
├── footer.php # Site footer
├── front-page.php # Homepage template
├── index.php # Fallback template
├── style.css # Theme declaration (headers only)
└── screenshot.png # Theme preview image
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 Changed · +36 lines 89951f3ef1bc
- 7d ago Changed · +13 lines 0759302eb4d9
- 10d ago First seen · 671 lines · 25 tokens per session scan A c3505d9b8938
wp-theme-standards is a skill published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 6,273 once invoked, about $0.0001 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
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
design-with-claude
Use when design work needs a product designer's eye: auditing a codebase for design-system gaps, fixing WCAG contrast and unlabeled inputs, choosing type scales or spacing steps, reviewing UI that looks generic or AI-generated, or designing forms, tables, dashboards, navigation, checkout, onboarding, dark mode, and…
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", or "vs best practices".
color-audit
Color-only audit that extracts, evaluates, and recommends improvements for the project's color system. Use when the user asks to audit colors, run a color review or color audit, fix their colors, or work on the color palette or color system.
theme-builder
Build a light/dark theme from scratch or improve an existing one, with a complete surface, text, and interactive color system. Use when the user asks to build or create a theme, use the theme builder, or set up a light and dark theme.
layout-audit
Layout and spacing audit covering grid, spacing consistency, density, and responsive behavior. Use when the user asks to audit the layout, run a layout audit or grid audit, review spacing, or fix their spacing.