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 ux-acceptance-coordinatorgit 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/ux-acceptance-coordinator)<a href="https://agentmods.dev/skills/emdash-cms/emdash/ux-acceptance-coordinator"><img src="https://agentmods.dev/badge/skills/emdash-cms/emdash/ux-acceptance-coordinator/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/ux-acceptance-coordinator"><img src="https://agentmods.dev/badge/skills/emdash-cms/emdash/ux-acceptance-coordinator.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.00059 | $0.00677 |
| Opus 5.5 | $0.00024 | $0.00271 |
| Sonnet 5.5 | $0.00012 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
ux-acceptance-coordinator 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 1mo 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.
Coordinate UX acceptance testing
Run a goal-driven browser journey with a tester that has no repository context. Keep site preparation, private success checks, and product diagnosis in the coordinator context.
Prepare the run
-
Read the selected journey in
acceptance/journeys/. -
Check the journey's
statusandrequiresfrontmatter. If its status isneeds-profile, report the missing bootstrap requirements and stop. Do not substitute a simpler profile or relax the journey. -
Read its site profile in
acceptance/sites/and the portable tester instructions inacceptance/tester/SKILL.md. -
Choose the journey's target. Use Node unless the journey or change under test requires the Cloudflare runtime.
-
Start one disposable site:
pnpm ux:site:start -- --target node --profile editorial-small -
Keep the run ID, start URL, and run-data path from the command output. Never send the run-data file or API token to the tester.
Isolate the tester
Create the tester outside the repository checkout. Give it only:
- the contents of
acceptance/tester/SKILL.md; - the journey's
Tester briefsection; - the generated start URL;
- a writable location for its report and screenshots.
Do not give the tester AGENTS.md, repository skills, source files, route names, the coordinator checks, or implementation context. Do not describe a clean context as isolated when the selected agent mechanism still exposes the checkout. If the environment cannot create a separate context within the user's authorization, prepare the handoff and ask the user to launch it.
Use any agent implementation that provides browser control. Do not translate the brief into tool-specific click instructions.
Verify and report
Wait for the tester to finish or explicitly give up. Preserve its action log, screenshots, and report without rewriting its observations.
Run the journey's Coordinator checks independently. Prefer a read-only public API with the local token in the run-data file; use direct database inspection only when the public surface cannot establish the result. The tester's claim is not proof of completion.
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.
- 1mo ago First seen · 60 lines · 59 tokens per session scan A c65297e09fc6
ux-acceptance-coordinator is a skill published in the GitHub repository emdash-cms/emdash (13,830 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 677 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-09-03.
Other skills, from other repositories
playwright-page-objects
Use when creating page objects or refactoring Playwright E2E tests for better maintainability with Page Object Model patterns.
test-browser
Run browser tests on pages affected by current PR or branch.
playwright-praman-sap-testing
Package: playwright-praman Import: import { test, expect } from 'playwright-praman' Purpose: Primary instruction set for Praman AI agents (planner, generator, healer).
writing-browser-e2e-tests
Playwright E2E testing standards from authoritative docs/explanation/software-engineering/automation-testing/tools/playwright/ documentation.
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.
exploratory-testing
Guides session-based exploratory testing of a running interface or API: framing charters, choosing tours, citing a specification, contract, or design for every expected result, telling a defect from a gap, and staying non-destructive.