Borrowing it
Nothing to install: this file belongs to Atomic-Mail/atomic-mail-agentic. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Atomic-Mail/atomic-mail-agentic/main/AGENTS.mdgit clone --depth 1 https://github.com/Atomic-Mail/atomic-mail-agenticWrote 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/atomic-mail/atomic-mail-agentic/agents-md)<a href="https://agentmods.dev/instructions/atomic-mail/atomic-mail-agentic/agents-md"><img src="https://agentmods.dev/badge/instructions/atomic-mail/atomic-mail-agentic/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.
<a href="https://agentmods.dev/instructions/atomic-mail/atomic-mail-agentic/agents-md"><img src="https://agentmods.dev/badge/instructions/atomic-mail/atomic-mail-agentic/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02291 | $0.02291 |
| Opus 5.5 | $0.00916 | $0.00916 |
| Sonnet 5.5 | $0.00458 | $0.00458 |
| Haiku 4.5 | $0.00229 | $0.00229 |
Grade A, and why
atomic-mail-agentic 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 26d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents working in this repository.
What this repo is
Atomic Mail Agentic ships MCP and CLI clients for Atomic Mail—a hosted email inbox for AI agents. Everything built in this repo — the local stdio MCP server, the AgentSkill CLI, the LangChain tools, the Python parity layer — exposes three operations only: register, jmap_request, and help.
That is the client surface, not the product surface. The hosted remote MCP server at mcp.atomicmail.ai is a different artifact, built server-side, and exposes 11 tools (read_inbox, read_message, search_messages, send_email, reply_to_message, list_agents, search, fetch, run_preset, jmap_request, help). Do not "fix" a doc that mentions those tools by trimming it back to three.
Primary implementation: TypeScript on Deno (ts/). Python (py/) mirrors core behavior for parity; keep it aligned with shared assets.
Agent host → MCP or CLI → ts/src/lib → auth.atomicmail.ai → api.atomicmail.ai (JMAP)
Sibling repo: the server
Everything to the right of ts/src/lib in that diagram is built somewhere else.
The backend that implements auth.atomicmail.ai, api.atomicmail.ai, and
mcp.atomicmail.ai lives in a separate, private repository (agentic-mail).
It is not a submodule and it is not vendored here.
If you have it checked out locally, it may be a sibling of this repo (try
../agentic-mail or ../../agentic-mail); otherwise ask the operator.
If you do not have access to it — which is the normal case — then:
- Treat every server behavior as a fixed API contract, documented in
docs/on this side. Readdocs/rest-auth.md,docs/jmap.md,docs/oauth.md, anddocs/mcp-remote.mdbefore assuming what a request or response looks like. - Do not infer the contract from client code alone. The client is one implementation of it; it can be wrong, and it can be behind.
- When a change would require the server to change too, stop and say so rather than guessing. Shipping a client that sends a field no endpoint accepts is worse than not shipping: mocked tests pass, and the failure surfaces in production. Say which endpoint needs to change and hand it back to the operator.
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.
- 26d ago Changed · +1 lines · +93 tokens per session b4904cf16090
- 1mo ago First seen · 138 lines · 2,198 tokens per session scan A c5509baccf41
atomic-mail-agentic AGENTS.md is an instructions file published in the GitHub repository Atomic-Mail/atomic-mail-agentic (262 stars, last pushed yesterday), licensed MIT. It adds 2,291 tokens to every session, about $0.0092 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-30.
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).
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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).