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 agentmods add commands/siddik-web/wp-block-theme-converter/wp-variationgit clone --depth 1 https://github.com/siddik-web/wp-block-theme-converterWrote 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/commands/siddik-web/wp-block-theme-converter/wp-variation)<a href="https://agentmods.dev/commands/siddik-web/wp-block-theme-converter/wp-variation"><img src="https://agentmods.dev/badge/commands/siddik-web/wp-block-theme-converter/wp-variation.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.03106 |
| Opus 5 | $0.00013 | $0.01553 |
| Sonnet 5 | $0.00005 | $0.00621 |
| Haiku 4.5 | $0.00003 | $0.00311 |
Grade A, and why
wp-variation 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wp-variation
Purpose: Generate a WordPress block theme style variation — a styles/*.json file that overrides color, typography, and spacing from the base theme.json to create an alternative theme aesthetic.
When to Use
Trigger this command when:
- The user wants a dark, light, high-contrast, seasonal, or brand-alternate version of their theme
- The user says "color scheme", "variant", "skin", "dark mode", "alternate palette"
- A design system has multiple brand expressions (e.g., marketing vs. product, seasonal themes)
Do not use this command for per-page or per-block style changes — style variations apply globally to the entire site.
Workflow
Step 1: Gather Variation Details
Ask (or infer from context):
| Question | Default if silent |
|---|---|
| Variation name (human-readable) | Required — always ask |
| Variation slug (kebab-case file name) | Derived from name |
| What to change: colors, typography, spacing, or all three? | Colors only (most common) |
| Color palette overrides | Required if colors are changing |
| Font overrides | Optional — only if changing fonts |
| Spacing overrides | Optional — only if changing scale |
| Is this a global variation (appears in Site Editor) or a scoped variation (Section Style on a Group block)? | Global variation |
Global vs Scoped Variations:
| Global Style Variation | Section Style | |
|---|---|---|
| Applies to | Entire site | A single block instance |
| File location | styles/{{slug}}.json |
styles.blocks.core/group.variations.{{slug}} in theme.json |
| Appears in | Site Editor → Styles → Browse styles | Block toolbar → Styles |
| WordPress version | 6.0+ | 6.6+ |
If the user wants a variation for a single block (e.g., a "dark section" Group block), refer to references/modern-blocks.md — Section Styles section instead.
Step 2: State the Variation Plan
VARIATION PLAN: {{Variation Name}}
File: styles/{{slug}}.json
Changes:
Colors: {{list color palette changes}}
Typography: {{list font changes, or "no changes"}}
Spacing: {{list spacing changes, or "no changes"}}
Elements: {{list element style 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.
- 5d ago First seen · 387 lines · 25 tokens per session scan A 2f6a74e75d93
wp-variation is a command published in the GitHub repository siddik-web/wp-block-theme-converter (45 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 3,106 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-30.
Other commands, from other repositories
design-audit
Audit an existing HTML/CSS design. Deterministic checks only (contrast, fonts, colors, states, dark mode) plus a visual pass. No generation.
responsiveness-check
Test responsive layout across viewport widths.
shadcn-ui
Install and configure shadcn/ui components.
design-page
New page or screen in an existing project. Skips design-system creation — reuses the existing design-system.md tokens.
design
Full design pipeline for a web or web-app target: brief → tokens → generation → motion → review. Use /design:mobile for iOS/Android instead.
start-13-4
Command "start-13-4" from minicoohei/ai-agent-camp, covering 🎓 lesson 13-4: 実際に動くlp作成（html/css/js）, 📍 このセッションでやること, 🎯 準備チェック, 🚀 step 1: コード化ガイドラインの取得 and 🚀 step 2: プロジェクト構造の作成.