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 skills/emdash-cms/emdash/wordpress-theme-to-emdashnpx skills add emdash-cms/emdash --skill wordpress-theme-to-emdashgit clone --depth 1 https://github.com/emdash-cms/emdashWhat 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.00072 | $0.00876 |
| Opus 5 | $0.00036 | $0.00438 |
| Sonnet 5 | $0.00014 | $0.00175 |
| Haiku 4.5 | $0.00007 | $0.00088 |
Grade A, and why
wordpress-theme-to-emdash 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 yesterday.
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Theme to EmDash
Port WordPress themes to EmDash in six phases. Read the phase file before starting each phase.
Critical Rules
- Copy scaffold first - Start every theme by copying
scaffold/from this skill - Take screenshots of demo - Identify the demo URL and capture all page types using agent-browser before starting work
- No hard-coded content - Use
getSiteSettings()for title/tagline,getMenu()for navigation - Server-rendered pages - Never use
getStaticPaths()for EmDash content - Astro 6 - Use
ClientRouternotViewTransitions, Zod 4 syntax, Node 22+ - Use emdash Image component - For all images, import Image from "emdash/ui"
Phases
| Phase | File | Summary |
|---|---|---|
| 1 | phases/1-discovery.md |
Download theme, screenshot demo, capture images |
| 2 | phases/2-design.md |
Extract CSS variables, fonts, colors |
| 3 | phases/3-templates.md |
Convert PHP templates to Astro |
| 4 | phases/4-dynamic.md |
Site settings, menus, taxonomies, widgets |
| 5 | phases/5-seed.md |
Create seed file with demo content |
| 6 | phases/6-verify.md |
Screenshot, compare, iterate, build |
Checklist
Setup
- Copy
scaffold/to new theme directory. Unless otherwise specified by the user, make this a subdirectory ofthemes/and name it after the WordPress theme (e.g.,themes/twentytwentyfour/). - Rename folder, update
package.json - Verify build:
pnpm build
Phase 1: Discovery
- Theme source downloaded
- Demo site identified
-
discovery/folder created withscreenshots/,images/,notes.md - All page types screenshotted
- Sample images downloaded
Phase 2: Design
- CSS variables in
global.css - Fonts loading
- Colors match demo
What ships with it
29 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- phases/1-discovery.md 5.3 KB
- phases/2-design.md 2.7 KB
- phases/3-templates.md 3.4 KB
- phases/4-dynamic.md 3.3 KB
- phases/5-seed.md 4.8 KB
- phases/6-verify.md 2.9 KB
- references/astro-essentials.md 26 KB
- references/concept-mapping.md 15 KB
- references/design-extraction.md 7.2 KB
- references/emdash-api.md 10 KB
- references/template-patterns.md 17 KB
- scaffold/astro.config.mjs 576 B runs code
- scaffold/CHECKLIST.md 4.1 KB
- scaffold/package.json 530 B
- scaffold/public/favicon.svg 257 B
- scaffold/README.md 2.8 KB
- scaffold/src/components/PostCard.astro 1.1 KB
- scaffold/src/env.d.ts 85 B runs code
- scaffold/src/layouts/Base.astro 1.6 KB
- scaffold/src/live.config.ts 500 B runs code
- scaffold/src/pages/404.astro 349 B
- scaffold/src/pages/categories/[slug].astro 1.3 KB
- scaffold/src/pages/index.astro 1.2 KB
- scaffold/src/pages/pages/[slug].astro 681 B
- scaffold/src/pages/posts/[slug].astro 2.2 KB
- scaffold/src/pages/posts/index.astro 1.0 KB
- scaffold/src/pages/tags/[slug].astro 1.2 KB
- scaffold/src/styles/global.css 4.0 KB
- scaffold/tsconfig.json 173 B
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.
- yesterday First seen · 84 lines · 72 tokens per session scan A 301e9f7972b0
wordpress-theme-to-emdash is a skill published in the GitHub repository emdash-cms/emdash (12,111 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 876 once invoked, about $0.0004 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 skills, from other repositories
wordpress-plugin-to-emdash
Port a WordPress plugin to EmDash CMS. Use this skill when asked to migrate, convert, or port a WordPress plugin, theme functionality, or custom post type to EmDash. Provides concept mapping and implementation patterns.
building-emdash-site
Build and customize EmDash CMS sites on Astro. Use when creating pages, defining collections, writing seed files, querying content, rendering Portable Text, setting up menus/taxonomies/widgets, configuring deployment, or any task involving an EmDash-powered Astro site. Assumes basic Astro knowledge but provides all…
emdash-cli
Use the EmDash CLI to manage content, schema, media, and more. Use this skill when you need to interact with a running EmDash instance from the command line — creating content, managing collections, uploading media, generating types, or scripting CMS operations.
emdash-github-actions
Sets up GitHub Actions CI/CD workflows for EmDash plugins — TypeScript type-checking, ESLint linting, Vitest testing, npm publishing, and automated releases. ALWAYS use this skill when a user wants to create, add, set up, or configure GitHub Actions, CI/CD, automated checks, or deployment workflows for an EmDash…
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
agent-browser
Browser automation for testing and verification. Use when you need to interact with web UIs, verify visual changes, fill forms, or capture screenshots.