skill-no-em-dashes: Instructions file for Codex

AGENTS.md

skill-no-em-dashes AGENTS.md is an instructions file for Codex, OpenCode from exmergo/skill-no-em-dashes. It costs 744 tokens per session, scanned A, original, MIT.

A repository-wide writing policy that bans em dashes and look-alike punctuation used in their place.

In plain words
What is it for?
Use it when writing or editing project text, especially when applying the rules from the repository's AGENTS.md file.
Why use it?
It makes prose follow a deliberate punctuation style across documentation, code comments, commits, emails, and other text.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is exmergo/skill-no-em-dashes's own configuration. It tells Codex and OpenCode how to work on skill-no-em-dashes itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything skill-no-em-dashes configures →

Reuse

Borrowing it

Nothing to install: this file belongs to exmergo/skill-no-em-dashes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/exmergo/skill-no-em-dashes/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/exmergo/skill-no-em-dashes

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for skill-no-em-dashes AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/exmergo/skill-no-em-dashes/agents-md/github.svg)](https://agentmods.dev/instructions/exmergo/skill-no-em-dashes/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/exmergo/skill-no-em-dashes/agents-md"><img src="https://agentmods.dev/badge/instructions/exmergo/skill-no-em-dashes/agents-md/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.

agentmods 80×15 button for skill-no-em-dashes AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/exmergo/skill-no-em-dashes/agents-md"><img src="https://agentmods.dev/badge/instructions/exmergo/skill-no-em-dashes/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 744 This file is loaded in full into every session.
When invoked 744 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00744 $0.00744
Opus 5.5 $0.00298 $0.00298
Sonnet 5.5 $0.00149 $0.00149
Haiku 4.5 $0.00074 $0.00074

Measured 1mo ago against content hash 340bad076767, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

skill-no-em-dashes AGENTS.md 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.

AGENTS.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writing style: no em dashes

These rules apply to any prose you write or edit: drafts, documentation, commit messages, pull request descriptions, comments, emails, marketing copy, and essays. The goal is writing that contains no em dashes and is built from sentences that never reach for one in the first place.

Why it matters: heavy em-dash use is one of the most recognizable fingerprints of machine-written text, and removing it forces tighter, more deliberate sentences.

The rule

  1. Never use an em dash (the character U+2014) as punctuation.
  2. Do not smuggle the same pause back in with a look-alike. These are banned when they do an em dash's job: a double hyphen (word--word or a spaced --), a hyphen padded with spaces (-), a stray en dash (U+2013) between words, and the horizontal bar (U+2015).
  3. Replace the construction with real punctuation, roughly in this order: comma, semicolon, colon, period, parentheses. When a plain swap reads awkwardly, recast the sentence rather than forcing a substitute.

Match the replacement to the job

An em dash is almost always doing one of a few jobs. Identify it, then replace it. In the examples below, [em dash] marks where the original reached for one.

  • Dramatic reveal ("She wanted one thing [em dash] to win"): use a colon, or split into two sentences.
  • "Not X but Y" pivot ("This isn't a tool [em dash] it's a platform"): recast as "This is a platform, not just a tool", or use a semicolon.
  • Interruptive aside ("The plan [em dash] which nobody liked [em dash] was scrapped"): use commas for a mild aside, parentheses for a true one.
  • Two joined clauses ("It compiles [em dash] and it's fast"): use a semicolon, a comma plus conjunction, or two sentences.
  • Summary dash ("Speed, clarity, polish [em dash] that's the goal"): recast around a colon, or split into sentences.
  • Interrupted dialogue: use a hard stop carried by narration, or an ellipsis for a line that trails off. This is the one job with no clean comma or semicolon swap.

Read the full file on GitHub · 63 lines

Changes

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.

  1. 1mo ago First seen · 63 lines · 744 tokens per session scan A 340bad076767

Subscribe to this mod's changes

skill-no-em-dashes AGENTS.md is an instructions file published in the GitHub repository exmergo/skill-no-em-dashes (11 stars, last pushed 4mo ago), licensed MIT. It adds 744 tokens to every session, about $0.0030 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-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens