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/dmorrill/gmail-mcp-multi/claude-mdgit clone --depth 1 https://github.com/dmorrill/gmail-mcp-multiWrote 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/dmorrill/gmail-mcp-multi/claude-md)<a href="https://agentmods.dev/instructions/dmorrill/gmail-mcp-multi/claude-md"><img src="https://agentmods.dev/badge/instructions/dmorrill/gmail-mcp-multi/claude-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.00248 | $0.00248 |
| Opus 5 | $0.00124 | $0.00124 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
gmail-mcp-multi CLAUDE.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 3d 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.
What it actually says
Gmail MCP Multi — Claude Development Guidelines
What This Is
MCP server that provides Gmail access across multiple accounts. Lets AI assistants search, read, send, and manage email across personal and work accounts with a single tool.
Tech Stack
- Runtime: Node.js, TypeScript
- Protocol: MCP (Model Context Protocol) via @modelcontextprotocol/sdk
- Auth: Google OAuth 2.0 (browser-based flow)
- Storage: Local JSON file for credentials
Architecture Principles
- Each account has a friendly alias (e.g., "personal", "work")
- OAuth tokens stored locally, auto-refreshed
- Tools are MCP-standard: list_accounts, authenticate, search_emails, read_email, send_email, modify_email, list_labels
- All tools take an
accountparameter to specify which mailbox
Current State
- PR #7 has the full initial implementation ready to merge
- Closes issues #1-#5
- Needs testing with real Gmail accounts before merge
Development
npm install
npm run build
npm run dev # for watch mode
Testing
npm test
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.
- 3d ago First seen · 34 lines · 248 tokens per session scan A 9b772df4a4a2
gmail-mcp-multi CLAUDE.md is an instructions file published in the GitHub repository dmorrill/gmail-mcp-multi (5 stars, last pushed 5mo ago), licensed MIT. It adds 248 tokens to every session, about $0.0012 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.