imap-mcp: Instructions file for Codex

AGENTS.md

imap-mcp AGENTS.md is an instructions file for Codex, OpenCode from lswith/imap-mcp. It costs 3,255 tokens per session, scanned A, original, MIT.

A repository instruction file for imap-mcp, an IMAP email-to-MCP server running on Cloudflare Workers.

In plain words
What is it for?
It guides changes to the mail synchronisation path, database migrations, MCP tools, authentication, deployment, and tests.
Why use it?
It tells coding agents which files contain each part of the system, which documents to read, and where tests and logging belong.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md.

This is lswith/imap-mcp's own configuration. It tells Codex and OpenCode how to work on imap-mcp 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 imap-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to lswith/imap-mcp. 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/lswith/imap-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/lswith/imap-mcp

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 imap-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/lswith/imap-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/lswith/imap-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/lswith/imap-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/lswith/imap-mcp/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 imap-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/lswith/imap-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/lswith/imap-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,255 This file is loaded in full into every session.
When invoked 3,255 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.03255 $0.03255
Opus 5.5 $0.01302 $0.01302
Sonnet 5.5 $0.00651 $0.00651
Haiku 4.5 $0.00326 $0.00326

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

Security

Grade A, and why

imap-mcp 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 2mo 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 · 229 lines

How it starts

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

imap-mcp — rules for working in this repo

Generic IMAP → MCP server on Cloudflare Workers: one Worker, one package, at the repository root. CLAUDE.md is a symlink to this file.

This file is the rules. The reasoning behind them lives in docs/architecture.md — read it before changing the sync path, the schema, or anything that reaches a model. Deploy mechanics are docs/deploy.md; the auth modes are docs/authentication.md; the contribution contract is CONTRIBUTING.md.

Layout

src/index.ts exports the Worker's three entry points: fetch (MCP server), scheduled (sync enumeration), queue (fetch consumers).

  • src/imap/ — the mailbox interface; the only place cf-imap is imported.
  • src/sync/ — everything that speaks IMAP. Write-policy refusals live here.
  • src/mcp/ — auth gate, tools, untrusted-content envelope, audit log.
  • src/writes.ts — the WriteService contract between the two halves.
  • src/log.ts — the only file in src/ that may call console.*.
  • src/status.ts — the GET /status diagnostics document.
  • migrations/ — the D1 schema.

Tests: test/sync, test/mcp, test/imap/unit and test/repo run inside workerd against the repo's own wrangler.jsonc; test/imap/protocol runs the real cf-imap client against a scripted server under Node. A change to provider behaviour must come with a protocol-harness test (see CONTRIBUTING.md).

Commands

pnpm install         # single package, no workspace
pnpm run lint        # biome check;  lint:fix to write
pnpm run typecheck   # wrangler types + tsc --noEmit
pnpm run test        # vitest, both projects;  test:watch, test:coverage
pnpm run dead-code   # knip
pnpm run build       # wrangler deploy --dry-run
pnpm run dev         # wrangler dev (API-key mode locally)
pnpm run deploy      # d1 migrations apply + wrangler deploy, in that order
pnpm run db:migrate:local / db:migrate:remote

Read the full file on GitHub · 229 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. 2mo ago First seen · 229 lines · 3,255 tokens per session scan A 3aa864fe8222

Subscribe to this mod's changes

imap-mcp AGENTS.md is an instructions file published in the GitHub repository lswith/imap-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 3,255 tokens to every session, about $0.0130 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

imap-mcp AGENTS.md compared with instructions from other repositories

imap-mcp AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
imap-mcp AGENTS.mdlswith/imap-mcpInstructions file01mo agoMITA3,255Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode