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/as-j/fastmail-mcp/agents-mdgit clone --depth 1 https://github.com/as-j/fastmail-mcpWrote 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/as-j/fastmail-mcp/agents-md)<a href="https://agentmods.dev/instructions/as-j/fastmail-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/as-j/fastmail-mcp/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.1 | $0.00826 | $0.00826 |
| Opus 5 | $0.00413 | $0.00413 |
| Sonnet 5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
fastmail-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 5d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.
Commands
npm run build # Compile TypeScript to dist/
npm run dev # Run directly with tsx (no build needed)
npm start # Run compiled output (requires build first)
npm test # Run all tests
tsx --test src/jmap-client.test.ts # Run a single test file
Architecture
This is a Model Context Protocol (MCP) server that exposes 28 tools for interacting with Fastmail email via the JMAP protocol.
Source Files
src/auth.ts—FastmailAuthclass: holds API token, builds auth headers and endpoint URLs. Simple, rarely changes.src/jmap-client.ts— Core JMAP client (JmapClientclass). All email/mailbox/attachment/search operations live here. Makes JMAP method calls viamakeRequest(), handles session bootstrapping, identity resolution, and JMAP result references (#idswithresultOffor chained calls).src/mcp-server.ts— MCP server factory and tool handlers. Registers all 28 tools, handles request dispatch, coerces JSON-encoded string args from web clients, normalizes address arrays, and resolves Fastmail config into per-session runtime contexts.src/http-server.ts— HTTP transport/session manager. Creates isolated MCP server instances per HTTP session, enforces body/session limits, expires idle sessions, and returns structured JSON-RPC errors for malformed HTTP requests.src/index.ts— Startup entry point. Chooses stdio vs HTTP mode and delegates to the appropriate server bootstrap code.
Key Patterns
JMAP chaining: Many operations use JMAP result references — e.g., a query call returns an ID, and a subsequent get call references it with "#ids": {"resultOf": "...", "name": "...", "path": "/ids"}. This avoids two round trips.
Arg coercion in mcp-server.ts: The coerceArgs function handles the case where web UIs send tool arguments as JSON strings instead of parsed objects. Any new tools that accept arrays or objects need to be supported there.
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.
- 5d ago First seen · 49 lines · 826 tokens per session scan A 8e04599b3732
fastmail-mcp AGENTS.md is an instructions file published in the GitHub repository as-j/fastmail-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 826 tokens to every session, about $0.0041 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).