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-plugin-to-emdashnpx skills add emdash-cms/emdash --skill wordpress-plugin-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-plugin-to-emdash)<a href="https://agentmods.dev/skills/emdash-cms/emdash/wordpress-plugin-to-emdash"><img src="https://agentmods.dev/badge/skills/emdash-cms/emdash/wordpress-plugin-to-emdash.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.00052 | $0.03301 |
| Opus 5 | $0.00026 | $0.01650 |
| Sonnet 5 | $0.00010 | $0.00660 |
| Haiku 4.5 | $0.00005 | $0.00330 |
Grade A, and why
wordpress-plugin-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 4d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Porting WordPress Plugins to EmDash
This skill maps WordPress concepts to their EmDash equivalents for plugin porting. For general plugin authoring details (plugin structure, definePlugin(), hooks, storage, admin UI, etc.), use the creating-plugins skill.
Migration Approach
- Understand the plugin — What does it do, not how
- Identify concepts — Content types, admin pages, hooks, shortcodes
- Map to EmDash — Use the tables below
- Implement in TypeScript — Clean room, not line-by-line port. Use the creating-plugins skill for implementation details.
- Test behaviour — Same result, different implementation
Concept Mapping
Content & Data
| WordPress | EmDash | Notes |
|---|---|---|
register_post_type() |
SchemaRegistry.createCollection() |
Via Admin API or seed file |
register_taxonomy() |
_emdash_taxonomy_defs table |
Hierarchical or flat, attached to collections |
register_meta() / ACF |
Collection fields via SchemaRegistry | All become typed schema fields |
get_post_meta() |
entry.data.fieldName |
Direct typed access |
get_option() |
getSiteSetting() / ctx.kv |
Site settings or plugin-namespaced KV |
WP_Query |
getEmDashCollection() |
Runtime queries with filters |
get_post($id) |
getEmDashEntry(collection, slug) |
Returns entry or null |
wp_insert_post() |
POST /_emdash/api/content/{type} |
REST API |
wp_update_post() |
PUT /_emdash/api/content/{type}/{id} |
REST API |
wp_delete_post() |
DELETE /_emdash/api/content/{type}/{id} |
Soft delete |
| Custom tables | Plugin storage collections | ctx.storage.collectionName.put/get/query |
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.
- 4d ago First seen · 298 lines · 52 tokens per session scan A 7fd2a9bd9952
wordpress-plugin-to-emdash is a skill published in the GitHub repository emdash-cms/emdash (12,159 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 3,301 once invoked, about $0.0003 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.
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.
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-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.