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/sous-chefs/emacs/agents-mdgit clone --depth 1 https://github.com/sous-chefs/emacsWrote 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/instructions/sous-chefs/emacs/agents-md)<a href="https://agentmods.dev/instructions/sous-chefs/emacs/agents-md"><img src="https://agentmods.dev/badge/instructions/sous-chefs/emacs/agents-md.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 | $0.00795 | $0.00795 |
| Opus 5 | $0.00398 | $0.00398 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
emacs 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 4d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Cookbook Purpose
Provides the emacs_package resource for installing Emacs
Agent Findings
- This cookbook is in an incremental modernization pass. Preserve existing public recipes and attributes unless a later full migration is explicitly selected.
- Dependency management should use
Policyfile.rb; do not reintroduce Berkshelf.
Known Limitations
Package Availability
GNU Emacs does not publish a separate vendor APT or RPM repository for this cookbook to manage. This cookbook installs from each platform's standard package repositories.
APT (Debian/Ubuntu)
- Ubuntu 24.04 LTS publishes
emacs,emacs-nox, and GUI variants from theemacssource package. Theemacs-noxpackage is published foramd64,arm64,armhf,ppc64el,riscv64, ands390x. - Debian 12 ships
emacsandemacs-noxin the main archive, with newer builds also available frombookworm-backports. - The cookbook default for Debian-family platforms is
emacs-nox, which matches the terminal-first package name used by both Debian and Ubuntu.
DNF/YUM (RHEL family / Fedora)
- Fedora publishes
emacsplusemacs-nw, the terminal-focused subpackage used by this cookbook. - RHEL 9 compatible repositories publish
emacs,emacs-common, andemacs-nox. Current EL9 package indexes show builds for at leastx86_64andaarch64. - This cookbook defaults to
emacson RHEL-family platforms becauseemacsis the stable package name across those repositories, while Fedora keeps a distinctemacs-nwpackage for terminal-only installs.
Arch Linux
- Arch Linux publishes both
emacsandemacs-noxin theextrarepository. - Current package metadata is published for
x86_64.
FreeBSD
- FreeBSD publishes
emacspackages through the ports tree, with flavors includingemacs,emacs-nox,emacs-canna, andemacs-wayland. - Current package indexes show
emacsandemacs-noxbuilds across multiple supported architectures, includingaarch64andamd64. - The legacy
editors/emacs-nox11path used by the old cookbook is obsolete under the current FreeBSD package flavor model.
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.
- 4d ago First seen · 76 lines · 795 tokens per session scan A 12af01bc844c
emacs AGENTS.md is an instructions file published in the GitHub repository sous-chefs/emacs (10 stars, last pushed 22d ago), licensed Apache-2.0. It adds 795 tokens to every session, about $0.0040 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 instructions, from other repositories
postfix copilot-instructions.md
Instructions for sous-chefs/postfix, covering copilot instructions for sous chefs cookbooks, repository overview, project structure, build and test system and environment setup.
postfix AGENTS.md
Instructions for sous-chefs/postfix: This cookbook manages Postfix through operating system packages and service/configuration files. It does not build Postfix from source.
varnish AGENTS.md
Instructions for sous-chefs/varnish, covering agents.md, agent guidance, package availability, apt (debian/ubuntu) and dnf/yum (rhel family).
ossec AGENTS.md
Instructions for sous-chefs/ossec, covering agents.md, cookbook purpose, agent findings, known limitations and package availability.
nfs AGENTS.md
Instructions for sous-chefs/nfs, covering agent notes, package availability, apt (debian/ubuntu), dnf/yum (rhel family, fedora, amazon linux) and zypper (suse).
beyondcompare AGENTS.md
Instructions for sous-chefs/beyondcompare, covering agents.md, cookbook purpose, agent findings, known limitations and package availability.