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.
git clone --depth 1 https://github.com/exmergo/skill-no-em-dashesWrote 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/rules/exmergo/skill-no-em-dashes/no-em-dashes)<a href="https://agentmods.dev/rules/exmergo/skill-no-em-dashes/no-em-dashes"><img src="https://agentmods.dev/badge/rules/exmergo/skill-no-em-dashes/no-em-dashes.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.1 | $0.00149 | $0.00149 |
| Opus 5 | $0.00075 | $0.00075 |
| Sonnet 5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
no-em-dashes 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 7d 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.
What it actually says
Follow the writing rules in AGENTS.md at the repository root.
In short: never use an em dash (U+2014) or its stand-ins (a double hyphen, a spaced
hyphen, a stray en dash, the horizontal bar) as sentence punctuation. Replace them with
commas, semicolons, colons, periods, or parentheses, and recast when a plain swap reads
awkwardly. Keep ordinary hyphens in compounds, ranges, code, and Markdown structure.
See AGENTS.md for the full playbook.
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.
- 7d ago First seen · 13 lines · 149 tokens per session scan A 85df5cb596da
no-em-dashes is a cursor rule published in the GitHub repository exmergo/skill-no-em-dashes (8 stars, last pushed 2mo ago), licensed MIT. It adds 149 tokens to every session, about $0.0007 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-31.
Other cursor rules, from other repositories
nextjs
Rules for Next.js projects (App Router and Pages Router).
vue
Rules for Vue (2 and 3) single-file components.
tests
Rules for test files — keep tests lean and pattern-matched.
context-delegate
Context Gatherer & External LLM Prompt Generator.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
enterprise-architect
Enterprise System Architect & High-Level Auditor.