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 instructions/generalaction/emdash/agents-mdgit clone --depth 1 https://github.com/generalaction/emdashWhat 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.05643 | $0.05643 |
| Opus 5 | $0.02821 | $0.02821 |
| Sonnet 5 | $0.01129 | $0.01129 |
| Haiku 4.5 | $0.00564 | $0.00564 |
Grade A, and why
emdash 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 yesterday.
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 — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Overview
Emdash is a local-first, cross-platform Electron app for running multiple AI coding agents in parallel. Each task is isolated in its own Git worktree and can run locally or over SSH, while the desktop app coordinates provider CLIs, ACP chat sessions, terminal sessions, issue and PR integrations, diff review, and release packaging.
Repository Structure
This is a pnpm workspace monorepo. The Electron app lives in
apps/emdash-desktop/ as @emdash/emdash-desktop; shared packages live under
packages/. Unless a path is prefixed with packages/ or another app, app paths
such as src/..., drizzle/, scripts/, and build/ are relative to
apps/emdash-desktop/.
Repo root:
.claude/- Local Claude agent settings for this checkout..github/- GitHub issue templates, reusable actions, CI, and release workflows.agents/- Agent-facing architecture, workflow, convention, integration, and risk docs.apps/emdash-desktop/- The Electron desktop app.apps/workspace-server/- Remote workspace server and its Docker-based dev stack.packages/chat-ui/- Shared transcript and ACP chat renderer with Storybook coverage.packages/core/- Transport-agnostic runtime primitives, including ACP session logic.packages/plugins/- Agent provider plugin definitions, hooks, and ACP adapters.packages/shared/- Shared primitives such as result types, logging, and markdown helpers.packages/theme/- Theme token codegen that emits the generated theme CSS.packages/ui/- Shared React UI components, theme tokens, recipes, and primitives.packages/wire/- Typed wire protocol contracts shared by app and workspace server.pnpm-workspace.yaml- Workspace package globs forapps/*andpackages/**.- Root config files -
package.json,nx.json,.nvmrc,.oxfmtrc.json,.oxlintrc.json, and lockfile/configuration owned at the workspace root.
Inside apps/emdash-desktop/:
build/- Electron packaging assets; avoid edits unless working on packaging/signing.drizzle/- Generated Drizzle SQL migrations and metadata.scripts/- Release, verification, and build support scripts.src/main/- Electron main process: bootstrap, Wire gateway, DB, and host services.src/entry/- Electron entry points:main.ts(main process) andpreload.ts, the typed preload bridge exposed to the renderer.src/renderer/- React composition shell, shared browser infrastructure, and tests.src/core/- Vertical slices with portable APIs, Node implementations, browser UI, and manifests.src/types/- Ambient and cross-cutting TypeScript declarations.tooling/- App-level development and test infrastructure not bundled into production.
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.
- yesterday First seen · 420 lines · 5,643 tokens per session scan A 75df1adfbc3c
emdash AGENTS.md is an instructions file published in the GitHub repository generalaction/emdash (5,548 stars, last pushed yesterday), licensed Apache-2.0. It adds 5,643 tokens to every session, about $0.0282 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 instructions, from other repositories
slopstop CLAUDE.md
Claude Code instructions for iansmith/slopstop, covering slopstop (ticket-plugin), universal project rules, slopstop-specific declarations, tests (per universal §1) and this repo is the tool the other projects' rules run on.
appwrite AGENTS.md
Instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
netdata AGENTS.md
AGENTS.md instructions for netdata/netdata, covering agents.md, goals, requirement language, mandatory development principles and sow system.
selfhost-ai CLAUDE.md
Instructions for kossakovsky/selfhost-ai, covering claude.md, project overview, core architecture, key files and installation flow.
SForum AGENTS.md
Instructions for zhuchunshu/SForum, covering agent guide, project intent, working principles, stack and directory map and commands.
redd-archiver CLAUDE.md
Instructions for 19-84/redd-archiver, covering claude.md, project overview, deviations from global standards, build & run commands and docker development (primary method).