Borrowing it
Nothing to install: this file belongs to jrenaldi79/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/jrenaldi79/google-workspace-mcp/master/CLAUDE.mdgit clone --depth 1 https://github.com/jrenaldi79/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/jrenaldi79/google-workspace-mcp/claude-md)<a href="https://agentmods.dev/instructions/jrenaldi79/google-workspace-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/jrenaldi79/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.01137 | $0.01137 |
| Opus 5 | $0.00568 | $0.00568 |
| Sonnet 5 | $0.00227 | $0.00227 |
| Haiku 4.5 | $0.00114 | $0.00114 |
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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - @presto-ai/google-workspace-mcp
Project Overview
This is a minimal npm distribution wrapper for the upstream gemini-cli-extensions/workspace Google Workspace MCP server.
Purpose: Enable easy installation via npx @presto-ai/google-workspace-mcp for employees to access Google Workspace services (Gmail, Calendar, Drive, Docs, Sheets, Chat) from Claude Desktop/Code.
Philosophy: This project is a glorified shim and CI/CD pipeline. We do NOT maintain custom code - we simply package upstream for npm distribution.
What This Project Does
- Syncs source from upstream - All code in
src/comes directly fromgemini-cli-extensions/workspace - Customizes paths.ts only - Changes token storage to
~/.config/google-workspace-mcp/instead of project root - Publishes to npm - Makes it installable via
npx
What This Project Does NOT Do
- No custom tests (upstream handles testing)
- No custom linting infrastructure
- No custom features or modifications
- No divergence from upstream behavior
Essential Commands
npm install # Install dependencies
npm run build # Build TypeScript → dist/
npm link # Test locally
google-workspace-mcp --auth # Authenticate
Project Structure
google-workspace-mcp/
├── .github/workflows/
│ ├── publish.yml # Publishes to npm on GitHub release
│ └── sync-and-publish.yml # Daily sync from upstream
├── bin/
│ └── cli.js # Entry point (shebang script)
├── src/ # SYNCED FROM upstream (do not modify)
│ └── utils/
│ └── paths.ts # ONLY file we customize
├── dist/ # Built output (gitignored)
├── esbuild.config.js # From upstream
├── package.json # Our npm config
└── README.md
The One Customization: paths.ts
We override src/utils/paths.ts to store tokens in a persistent user config directory:
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 · 150 lines · 1,137 tokens per session scan A 9c87918e881c
google-workspace-mcp CLAUDE.md is an instructions file published in the GitHub repository jrenaldi79/google-workspace-mcp (3 stars, last pushed 6mo ago), licensed MIT. It adds 1,137 tokens to every session, about $0.0057 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).
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.