google-workspace-mcp: Instructions file for GitHub Copilot

.github/instructions/general.instructions.md

google-workspace-mcp general.instructions.md is an instructions file for GitHub Copilot from tom275275/google-workspace-mcp. It costs 1,123 tokens per session, scanned A, a copy of google_workspace_mcp general.instructions.md, MIT.

A set of review instructions for a Google Workspace MCP server. MCP is a standard way for an AI agent to call tools such as Gmail, Calendar, Drive, and Sheets.

In plain words
What is it for?
Reviewing changes to FastMCP-based Python tools, checking their generated input schemas, and assessing validation, typing, authentication, concurrency, and tests.
Why use it?
It gives code reviewers a consistent checklist for checking tool inputs, errors, types, and protocol compliance, while helping them skip low-value comments.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is tom275275/google-workspace-mcp's own configuration. It tells GitHub Copilot how to work on google-workspace-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything google-workspace-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to tom275275/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.

Copy the file
curl -O https://raw.githubusercontent.com/tom275275/google-workspace-mcp/main/.github/instructions/general.instructions.md
Clone the repo
git clone --depth 1 https://github.com/tom275275/google-workspace-mcp

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for google-workspace-mcp general.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tom275275/google-workspace-mcp/general.svg)](https://agentmods.dev/instructions/tom275275/google-workspace-mcp/general)
Your own site
<a href="https://agentmods.dev/instructions/tom275275/google-workspace-mcp/general"><img src="https://agentmods.dev/badge/instructions/tom275275/google-workspace-mcp/general.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,123 This file is loaded in full into every session.
When invoked 1,123 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 98% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01123 $0.01123
Opus 5 $0.00562 $0.00562
Sonnet 5 $0.00225 $0.00225
Haiku 4.5 $0.00112 $0.00112

Measured 6d ago against content hash 952f79f8160d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

google-workspace-mcp general.instructions.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 6d 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.

Origin

This is a copy

98% identical to google_workspace_mcp general.instructions.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/instructions/general.instructions.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert Python engineer with a specific expertise around FastMCP-based Python Model Context Protocol (MCP) servers.

📄 Project Context

This repository (google_workspace_mcp) is a production‑grade FastMCP server that exposes Google Workspace‑tooling (Gmail, Calendar, Drive, Docs, Sheets, Slides, Chat, Tasks, Forms, Contacts, Search) to LLM clients. Key architectural pillars:

  • FastMCP 3.x for server/runtime, tool registration, validation and transports.
  • Async Google client libraries with OAuth 2.1 desktop‑flow and multi‑user token caching.
  • Strict typing & pydantic‑v2 models for request/response schemas.
  • High‑concurrency, stateless worker model (FastAPI/Starlette under the hood).
  • Automated CI (PyPI release + Docker/Helm chart) and >90 % unit + integration test coverage.

🎯 Review Goals & Priorities

  1. Correctness & Protocol Compliance

    • Ensure new/modified tools conform to the MCP JSON‑Schema generated by FastMCP (@mcp.tool).
    • Validate that their signatures remain LLM‑friendly (primitive or Pydantic types only).
    • Check that strict_input_validation is left False unless there’s a compelling reason, to avoid brittle clients.
  2. Security & Privacy

    • No secrets, refresh tokens or PII logged or leaked in exceptions or event streams.
    • All outbound Google API calls must respect end‑user OAuth scopes – least privilege.
    • Rate‑limit & quota errors should be caught and surfaced as MCP ToolExecutionError.
  3. Robustness & Performance

    • Prefer asyncio Google APIs (via google-apis-async) or run blocking calls inside run_in_executor.
    • Avoid long‑running operations (>30 s) inside request context – instruct to stream partial results or schedule background tasks.
    • Check that pagination helpers (list_page_size, nextCursor) are used for large result sets to avoid oversize LLM responses.
  4. API Design & UX

    • Tool names: imperative, camelCase, ≤3 words.
    • Descriptions: single sentence in present tense; include parameter hints.
    • Response payloads: concise, redact verbose HTML/e‑mail bodies by default; offer links or IDs to fetch full content.
    • Tag new beta/experimental tools with tags={"beta"} so they can be excluded easily.

Read the full file on GitHub · 105 lines

Changes

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.

  1. 6d ago First seen · 105 lines · 1,123 tokens per session scan A 952f79f8160d

Subscribe to this mod's changes

google-workspace-mcp general.instructions.md is an instructions file published in the GitHub repository tom275275/google-workspace-mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 1,123 tokens to every session, about $0.0056 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to google_workspace_mcp general.instructions.md, differing in 2 lines, and is treated as a copy.

Related

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens