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/abdulkader-safi/wp-to-code/wp-themegit clone --depth 1 https://github.com/Abdulkader-Safi/wp-to-codeWhat 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.00019 | $0.00477 |
| Opus 5 | $0.00010 | $0.00238 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
wp-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 2d 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
Run the token census: $ARGUMENTS.
NODE_PATH="${CLAUDE_PLUGIN_DATA}/node_modules" \
node "${CLAUDE_PLUGIN_ROOT}/scripts/theme.mjs"
Reads computed styles across every mirrored page, not the stylesheets. Builder CSS is generated and unreadable, and the browser has already resolved it.
For a Gutenberg site, read theme.json from the source instead. It is already a token file.
Naming
Type tokens are named by pixel value. --text-23: 23px. When a measurement reads 23px/27.6px you write text-23 leading-[27.6px] with no arithmetic in between, and the name cannot drift from what it means.
Enumerate every size before writing any markup. A token used but never defined emits nothing, the element silently inherits, and section heights can stay correct while the text renders at half size. The census output is the complete list; put all of it in the token file even if some sizes appear once.
Colours and font families come out numbered with usage counts. Name them yourself. The most-used family is usually body text and the rarest is usually the display face, but that is a judgement about the design, and a counter cannot make it.
Breakpoints
The census separates real boundaries from noise. A real breakpoint shows up as an adjacent pair: a rule at max-width: 767px and its counterpart at min-width: 768px. Isolated widths are plugin defaults and are not part of this site's design.
Put the real boundaries in the config's viewports so /wp-diff checks each one. A section that matches at 1440 and collapses at 390 is the most common way a port ships broken.
Line heights
The size/line-height table is the useful half of the output. Any pair ending /normal is unresolved: that element inherits roughly 1.5em and the design almost certainly wants less. Resolve each one against the original before using it.
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.
- 2d ago First seen · 35 lines · 19 tokens per session scan A ea4a8ccef015
wp-theme is a command published in the GitHub repository Abdulkader-Safi/wp-to-code (2 stars, last pushed 13d ago), licensed MIT. It adds 19 tokens to every session and 477 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 commands, from other repositories
pack
Bundle every designlang output (DTCG tokens, Tailwind, shadcn, Figma vars, motion, anatomy, Storybook, prompts) into one polished design-system directory ready to zip and ship.
verify
Fidelity check — rebuild a page from the extracted tokens, pixel-diff it against the live site, and score how faithfully the tokens capture the design.
battle
Head-to-head graded battle card between two sites — eight dimensions, bar-by-bar, verdict line.
add-library
Kullanıcı "kütüphane ekle", "library ekle", "tasarım sistemi ekle", "design system ekle" dediğinde bu komutu uygula.
test
Run tests and ensure code quality for the F-MCP ATezer server.
sheleg-design
Apply the SHELEG Design methodology (single-clock, layered, degrade-to-calm motion) to the current landing-page / hero / scroll-animation task — or its style packs to product UI (dashboards, admin, internal tools).