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 implementgit 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/implement)<a href="https://agentmods.dev/skills/emdash-cms/emdash/implement"><img src="https://agentmods.dev/badge/skills/emdash-cms/emdash/implement/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/implement"><img src="https://agentmods.dev/badge/skills/emdash-cms/emdash/implement.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.00035 | $0.01308 |
| Opus 5.5 | $0.00014 | $0.00523 |
| Sonnet 5.5 | $0.00007 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
implement 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 6d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement
A maintainer explicitly asked you to build the issue's requested change. Treat the issue body and directive as the specification. This lane is for enhancements and directed changes; do not invent a bug verdict or describe an enhancement as reproduced.
Delivery priorities
The working candidate is the deliverable; tests are evidence for it. TDD controls ordering for a confirmed bug, not how much of the run test construction may consume. Enhancements do not need a failing test first.
- Use an existing test file, helper, and configuration at the lowest layer that proves the requested behavior. One focused regression case is normally enough.
- Do not add a test configuration, package script, custom harness, or dependency inspection solely to make the change testable. Do not inspect
node_modulesunless the requested behavior depends on third-party internals. - If one test approach has not converged after three attempts or about ten minutes, stop using it. Choose a lower-level seam or implement the scoped change and report the test gap. For a confirmed bug, do not claim completion without a meaningful regression test; publish the partial candidate and state what is missing.
- Protect the final fifteen minutes for metadata, one verification pass,
publish_candidate, and reporting. Stop optional investigation before that window. - Update the public plan after the first source edit and when moving from editing to verification or publication. Do not leave it on an obsolete test step.
Procedure
- Read
AGENTS.mdand the relevant implementation, tests, and contributor guidance before editing. - The harness installs dependencies and builds the base workspace before this turn. Do not run
pnpm install, the rootpnpm build, or a pre-edit lint baseline. - Choose the smallest final verification set before editing: the focused behavior test, the checks under "Checks in this container", and a check-only formatter.
- Resolve ambiguity from existing APIs, sibling code, and backwards-compatible behavior. If a missing decision would materially change the public contract, stop and report it instead of guessing.
- Edit through
edit_file,write_file, or a shell command throughexec. Shell-produced changes are checkpointed into the durable workspace. Keep the change scoped to the request. Do not modify.github/workflowsor generated Lingui catalogs. - Add the smallest behavior-level test that uses existing infrastructure. For a directed bug fix, follow the repository's failing-test-first rule within the test-construction limit above.
- Finish every candidate edit before final verification. Run formatting through
execand add the changeset now, when a published package changed. If a transformation fails after writing files, repair or restore its checkpoint before continuing. - Run the planned final checks with
exec, once each on the final candidate. Fix failures caused by the change and rerun the affected check after editing. Do not hide failures with shell fallbacks. If a relevant failure remains, preserve the candidate and report it accurately instead of withholding the work from CI. - Call
publish_candidateafter the final checks, including when a check remains failing. The trusted tool commits and pushes only tobot/fix-<issue>through the issue-scoped Git proxy; never rungit commit,git push, or create a PR yourself. - Call
report_implementationexactly once. Setimplemented: trueonly after publication succeeds. Summarize the observable change and verification, not a bug verdict.
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.
- 6d ago Changed · +8 lines e7d384edde87
- 14d ago Changed 5664c8d6e854
- 1mo ago Changed 6ff30c775e2a
- 1mo ago First seen · 57 lines · 35 tokens per session scan A 6c8a0214781c
implement is a skill published in the GitHub repository emdash-cms/emdash (13,659 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,308 once invoked, about $0.0001 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
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.
webiny-api-logger-catalog
Name: Logger Import: import { Logger } from "webiny/api/logger" Source: @webiny/api-core/features/logger/index.ts Description: Structured logging with multiple log levels.
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.