Borrowing it
Nothing to install: this file belongs to AdamFerguson06/gmail-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.
curl -O https://raw.githubusercontent.com/AdamFerguson06/gmail-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/AdamFerguson06/gmail-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/adamferguson06/gmail-mcp/claude-md)<a href="https://agentmods.dev/instructions/adamferguson06/gmail-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/adamferguson06/gmail-mcp/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.1 | $0.00821 | $0.00821 |
| Opus 5 | $0.00411 | $0.00411 |
| Sonnet 5 | $0.00164 | $0.00164 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
gmail-mcp 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 7d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Commands
# Run all tests
python -m pytest tests/ -v
# Run a single test file
python -m pytest tests/test_config.py -v
# Run a single test
python -m pytest tests/test_config.py::test_load_config_success -v
# Install in development mode
pip install -e ".[test]"
# Verify credentials and API connectivity
gmail-reader test
# Run CLI with debug logging
gmail-reader list -v
Architecture
This is a read-only Gmail tool with two interfaces: a CLI (__main__.py) and an MCP server (mcp_server.py). Both share the same data layer.
Data Flow
CLI (__main__.py) ──┐
├──> reports.py (shared fetch functions) ──> client.py ──> Gmail API
MCP (mcp_server.py) ┘
config.py— Loads OAuth credentials from~/.env; also holds all tunable constants (rate limits, pagination limits, etc.) with env var overridesauth.py— OAuth 2.0 flow; POSIX-only (usesfcntlfor file locking)client.py—get_gmail_service()builds the API client;execute_gmail_request()wraps every API call with token-bucket rate limiting and retry logic (429 + 5xx)queries.py— Field mask constants (MESSAGE_LIST_FIELDS, etc.), date helpers, input validators (validate_query_length,validate_gmail_id)reports.py— Shared public functions (fetch_message_details,fetch_message_full_detail,fetch_thread_details,fetch_labels) used by both CLI and MCP server; also has CLI-specificprint_*functions and private helpers (_fetch_all_messages,_parse_headers,_parse_body,_format_date)mcp_server.py— MCP server with 6 tools; delegates data fetching toreports.py; wrapscall_tool()in HttpError/Exception catch to prevent crashes
Key Patterns
Lambda closures in loops — Always use default arguments to capture loop variables:
# Correct:
lambda mid=msg_id: service.users().messages().get(userId="me", id=mid).execute()
# Wrong (captures reference, gets last value):
lambda: service.users().messages().get(userId="me", id=msg_id).execute()
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.
- 7d ago First seen · 73 lines · 821 tokens per session scan A fda4189edc8c
gmail-mcp CLAUDE.md is an instructions file published in the GitHub repository AdamFerguson06/gmail-mcp (2 stars, last pushed 6mo ago), licensed MIT. It adds 821 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
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.
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).
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).
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.
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.