EmDash is a content management system for creating and managing websites, built with TypeScript and Astro and deployable on Cloudflare or Node.js with SQLite. It is for site owners and developers who want WordPress-like administration, templates, and plugins without PHP or separate hosting.
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 emdash-cms/emdash --skill wordpress-theme-to-emdashgit clone --depth 1 https://github.com/emdash-cms/emdashWrote 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/emdash-cms/emdash/wordpress-theme-to-emdash)<a href="https://agentmods.dev/skills/emdash-cms/emdash/wordpress-theme-to-emdash"><img src="https://agentmods.dev/badge/skills/emdash-cms/emdash/wordpress-theme-to-emdash/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/emdash-cms/emdash/wordpress-theme-to-emdash"><img src="https://agentmods.dev/badge/skills/emdash-cms/emdash/wordpress-theme-to-emdash.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.00057 | $0.00769 |
| Opus 5.5 | $0.00023 | $0.00308 |
| Sonnet 5.5 | $0.00011 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
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 17d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Port a WordPress theme to EmDash
Recreate the theme's relevant layouts and interactions as an Astro site backed by EmDash. Preserve the user's requested visual fidelity and feature scope; do not assume every WordPress template or demo feature belongs in the port.
Load building-emdash-site for current EmDash schema, query, rendering, caching, and seed patterns. When a live reference site is available, use the agent-browser CLI for rendered comparison; run agent-browser skills get core --full for its command reference.
Choose the evidence
Use the best available sources in this order:
- theme source and
theme.json, stylesheets, templates, andfunctions.php; - a live demo at representative desktop and mobile viewports;
- screenshots or design files supplied by the user;
- explicit design decisions where the source is ambiguous.
Do not infer that demo content or images share the theme code's license. Reuse an asset only when its license or the user's rights permit it; otherwise use a clearly licensed substitute with similar dimensions and visual weight.
Plan the port
Inventory only the page types, components, responsive states, and interactions needed for the requested site. Map WordPress responsibilities before implementing:
- PHP templates become Astro routes, layouts, and components.
- Custom post types, metadata, and taxonomies become EmDash collections, fields, and taxonomies.
- Theme Customizer values become site settings or explicit project configuration.
- Menu locations become named EmDash menus queried by templates.
- Sidebars and widgets become widget areas or ordinary Astro components.
- Shortcodes and plugin-owned behavior may require a separate plugin migration.
Read WordPress theme concept mapping when translating template hierarchy, functions.php registrations, template tags, hooks, widgets, or reusable blocks.
Dynamic EmDash content routes must remain server-rendered. Use the EmDash Image component for EmDash media fields; ordinary theme assets can use Astro's asset handling.
What ships with it
7 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.
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.
- 17d ago Changed f3aece779ce8
- 26d ago Changed · -24 lines · -15 tokens per session ec8e5ee4c36b
- 1mo ago 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 (13,659 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 769 once invoked, about $0.0002 per session on Opus 5.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
creating-plugins
Create EmDash CMS plugins with sandboxed hooks, routes, storage, content and media APIs, MCP tools, and declarative admin UI, or native React and Astro extensions. Use when scaffolding or implementing an EmDash plugin.
emdash-cli
Use the EmDash CLI to inspect and manage an EmDash instance from the command line, including content, schema, media, taxonomies, menus, search, authentication, seeds, migrations, generated types, and whole-site export and import.
wordpress-plugin-to-emdash
Analyze and port WordPress plugin behavior, custom post types, shortcodes, admin workflows, and stored data to current EmDash extension points. Use for WordPress-plugin migrations or when deciding which behavior belongs in an EmDash plugin, site schema, seed, or Astro code. Do not use for visual theme ports without…
building-emdash-site
Build the site-facing parts of an EmDash CMS project on Astro, including schema and seeds, content queries, Portable Text rendering, menus, taxonomies, widgets, and deployment configuration. Use for EmDash site and theme work; use creating-plugins instead when the task is plugin authoring alone.
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
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart. Do not use for ordinary review, style feedback, or general improvement suggestions.