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.
git clone --depth 1 https://github.com/ConlinJoe/ai-platformWrote 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/rules/conlinjoe/ai-platform/36-wordpress-theme)<a href="https://agentmods.dev/rules/conlinjoe/ai-platform/36-wordpress-theme"><img src="https://agentmods.dev/badge/rules/conlinjoe/ai-platform/36-wordpress-theme/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/rules/conlinjoe/ai-platform/36-wordpress-theme"><img src="https://agentmods.dev/badge/rules/conlinjoe/ai-platform/36-wordpress-theme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.01307 |
| Opus 5.5 | $0.00000 | $0.00523 |
| Sonnet 5.5 | $0.00000 | $0.00261 |
| Haiku 4.5 | $0.00000 | $0.00131 |
Grade A, and why
36-wordpress-theme 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress, Tailwind, and theme.json
Apply this rule only when the project uses WordPress together with
Tailwind and theme.json. That includes Radicle/Sage themes and other
WordPress themes on this combination.
Do not apply it to Laravel, React, Rails, or other non-WordPress
stacks. Do not apply it to WordPress projects that do not use both
Tailwind and theme.json.
Current-First Engineering in 00-platform still applies. Inspect the
installed WordPress and Tailwind versions and the CSS this project
actually generates. Handbook examples go stale: WordPress has emitted
both bare element selectors and :root :where(...) wrappers. Follow
the generated stylesheet for the installed version.
Source of truth
Project Tailwind tokens are the typography and color source of truth.
On Tailwind v4 that is the CSS-first theme (@theme and the version's
other theme APIs). On Tailwind v3 that is the v3 theme configuration.
Do not upgrade Tailwind to satisfy this rule.
Generate or align theme.json presets with those tokens so editors
get the approved fonts, sizes, and colors. Point palette, font-family,
and font-size presets at the CSS variables the Tailwind theme already
defines. WordPress preset variables (--wp--preset--color--*,
--wp--preset--font-size--*, and font-family presets) may alias those
tokens. Do not keep a second, independent set of color or type values
in theme.json.
Use theme.json for WordPress settings and for intentional content
defaults. Keep the file. Do not remove theme.json to escape a
cascade conflict.
Editorial typography
WordPress generates CSS from theme.json for both the block editor
and the public site. Top-level styles.elements for heading and
h1-h6 emit heading element selectors. Some blocks, including
core/paragraph, can emit an element selector such as p. Treat
lists the same way: a generated ul or ol rule with no content
scope is unscoped element typography.
Avoid that unscoped element typography. It can override Tailwind
utilities on custom page components. Tailwind v4 keeps utilities in
@layer utilities. Unlayered WordPress CSS beats layered utilities
even when the utility is more specific. Tailwind v3 utilities are
unlayered unless the project opted into layers. Read the actual
stylesheets for this project.
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 · 134 lines · 0 tokens per session scan A c3b410ef8eff
36-wordpress-theme is a cursor rule published in the GitHub repository ConlinJoe/ai-platform (2 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,307 tokens. 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-09-24.
Other cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
css
Troy stylesheet conventions, layout debugging, and minification.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
z-index
Z-index layering conventions for consistent stacking.