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/adinschmidt/fastmail-mcp/agents-mdgit clone --depth 1 https://github.com/adinschmidt/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/adinschmidt/fastmail-mcp/agents-md)<a href="https://agentmods.dev/instructions/adinschmidt/fastmail-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/adinschmidt/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 | $0.01333 | $0.01333 |
| Opus 5 | $0.00666 | $0.00666 |
| Sonnet 5 | $0.00267 | $0.00267 |
| Haiku 4.5 | $0.00133 | $0.00133 |
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 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This repo is a Bun + TypeScript MCP server for mail (JMAP) + calendar (CalDAV) + contacts (CardDAV). It is provider-generic; Fastmail works out of the box via legacy FASTMAIL_* env vars (the project began as fastmail-mcp).
Key paths:
src/index.tsMCP server + tool registration (domain-gated: mail/calendar/contacts register based on configured credentials orMCP_DOMAINS)src/bin/*mail-only (jmap-mcp) and calendar/contacts-only (dav-mcp) entry pointssrc/jmap/*JMAP auth/client/typessrc/dav/*CalDAV/CardDAV client helpers + iCal/vCard helperssrc/config.tsenv var loading — genericJMAP_*/DAV_*/CALDAV_URL/CARDDAV_URLvars withFASTMAIL_*fallbacks that imply Fastmail server URLs
Commands (Build / Lint / Test)
Package manager/runtime:
- Install deps:
bun install(lockfile:bun.lock) - Run dev server (watch):
bun run dev - Run server (stdio):
bun run start
Typecheck/build:
- Typecheck:
bun run typecheck - Build bundle to
dist/:bun run build - Clean build output:
bun run clean
Lint/format:
- No linter/formatter is currently configured (no ESLint/Prettier config in repo).
- Use
bun run typecheckas the primary quality gate. - If adding a formatter, prefer a repo-pinned tool (devDependency + config) rather than ad-hoc
bunx.
Tests:
- Bun's built-in runner (
*.test.tsfiles insrc/):- Run all:
bun test - Run one file:
bun test src/calendar-crud.test.ts - Run one test by name:
bun test -t "parses vCard" - Watch:
bun test --watch
- Run all:
Code Style (TypeScript / Imports / Formatting)
Module system:
- ESM +
moduleResolution: NodeNext(seetsconfig.json). - Local imports MUST use
.jsextensions in source (TypeScript will map them):- Good:
import { loadDavConfig } from './config.js' - Bad:
import { loadDavConfig } from './config'
- Good:
Imports:
- Prefer
node:protocol for Node built-ins:import { randomUUID } from 'node:crypto'. - Import order (keep blocks visually separated):
- Node built-ins (
node:*) - Third-party deps (
zod,tsdav, MCP SDK) - Local modules (
./foo.js,../bar.js)
- Node built-ins (
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 · 138 lines · 1,333 tokens per session scan A 88e5edfaaa20
fastmail-mcp AGENTS.md is an instructions file published in the GitHub repository adinschmidt/fastmail-mcp (0 stars, last pushed 26d ago), licensed MIT. It adds 1,333 tokens to every session, about $0.0067 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.