Borrowing it
Nothing to install: this file belongs to dguido/google-workspace-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/dguido/google-workspace-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/dguido/google-workspace-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/dguido/google-workspace-mcp/claude-md)<a href="https://agentmods.dev/instructions/dguido/google-workspace-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/dguido/google-workspace-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.01704 | $0.01704 |
| Opus 5 | $0.00852 | $0.00852 |
| Sonnet 5 | $0.00341 | $0.00341 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
google-workspace-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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Workspace MCP
MCP server providing Claude access to Google Drive, Docs, Sheets, Slides, Calendar, and Gmail.
Architecture
src/
├── index.ts # Entry point, MCP server setup, tool routing
├── auth/ # OAuth2 authentication
├── handlers/ # Tool implementations (drive, docs, sheets, slides, calendar, gmail, unified)
├── schemas/ # Zod validation schemas
├── tools/ # Tool definitions for MCP
├── utils/ # Shared utilities
└── prompts/ # MCP prompt definitions
Three-layer pattern: Tool Definitions → Schemas → Handlers → ToolResponse
Development
| Command | Purpose |
|---|---|
npm run build |
TypeScript check + bundle |
npm run typecheck |
Type check only |
npm run lint |
oxlint |
npm run format |
oxfmt |
npm run check |
typecheck + lint + format:check |
npm test |
Run tests (Vitest) |
npm run test:watch |
Watch mode |
npm run auth |
Run OAuth flow |
Navigating the codebase
# Find handler implementations
ast-grep --pattern 'export async function handle$_($$$)' --lang ts src/handlers
# Find schema definitions
ast-grep --pattern 'export const $_Schema = z.$_($$$)' --lang ts src/schemas
# Find tool definitions
rg "name: '" src/tools/definitions.ts
# Find all usages of a handler
rg "handleCreateTextFile" src
Serena (LSP symbol tools)
Use Serena's semantic tools when text search isn't enough:
| When you need to... | Use |
|---|---|
| Understand a file's structure | get_symbols_overview |
| Find where something is defined | find_symbol |
| Find all usages of a function/class/type | find_referencing_symbols |
| Rename across the entire codebase | rename_symbol |
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 · 173 lines · 1,704 tokens per session scan A db18852f2ad0
google-workspace-mcp CLAUDE.md is an instructions file published in the GitHub repository dguido/google-workspace-mcp (38 stars, last pushed 6mo ago), licensed MIT. It adds 1,704 tokens to every session, about $0.0085 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-30.
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).
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).
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.