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/dipseth/google_workspace_fastmcp2/claude-mdgit clone --depth 1 https://github.com/dipseth/google_workspace_fastmcp2Wrote 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/dipseth/google_workspace_fastmcp2/claude-md)<a href="https://agentmods.dev/instructions/dipseth/google_workspace_fastmcp2/claude-md"><img src="https://agentmods.dev/badge/instructions/dipseth/google_workspace_fastmcp2/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.00616 | $0.00616 |
| Opus 5 | $0.00308 | $0.00308 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
google_workspace_fastmcp2 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 4d 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Release / deployment pattern
- A release is a version bump merged to
main. .github/workflows/publish.yml runs on every push tomainand publishes to PyPI only ifversioninpyproject.tomldiffers from the previous commit (HEAD~1). No tags involved. - Every PR that should ship must bump the version in both places, kept in sync:
pyproject.toml→version = "X.Y.Z"uv.lock→ thegoogle-workspace-unlimitedpackage entry'sversion
- Title the release PR / merge commit
Release X.Y.Z — <summary>(see git history for examples). - Semver-ish: patch for fixes, minor for new tools/features or behavior-default changes.
- Downstream consumers: PyPI (
uvx google-workspace-unlimited) and Glama's Docker build (clones this repo and runsuv sync). The wheel must include all runtime packages — check[tool.hatch.build.targets.wheel]when adding a new top-level package dir (a missinglifespans/broke 2.4.x on PyPI).
Glama hosted deploy (admin build spec)
cmdArgumentsmust useuv run --no-sync— plainuv runrebuilds the package on every container start (~33s), blowing Glama's ~35s health-check timeout and marking the server "unhealthy" (503s on every request).buildSteps:uv sync --compile-bytecode, thenuv run --no-sync python -c 'import server' || trueto warm imports at build time (~12s cold start, measured).- Set
QDRANT_AUTO_LAUNCH=falsein hosted env vars (defaulttruetries to launch Qdrant via Docker, which doesn't exist in the container).
Python version
requires-python = ">=3.11,<3.13";.python-versionpins 3.12. Keep the pin — Glama auto-detects the Docker Python version from it and previously picked an incompatible 3.14 when the file was absent.
Pre-push checks
- Run both
ruff check .andruff format --check .— CI gates them separately. - Plugin skills are generated, never hand-edited.
plugins/google-workspace-unlimited/skills/is produced byuv run python scripts/generate_plugin_skills.pyfrom the same ModuleWrapper introspection the server uses at startup; CI fails if the committed copies drift (--check). After changing card/email/qdrant models, skill generators, orskills/skills_provider.py, regenerate and commit. - Production code must never import from
research/; TRM inference definitions live inadapters/.
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.
- 4d ago First seen · 28 lines · 616 tokens per session scan A 2d7e1331712d
google_workspace_fastmcp2 CLAUDE.md is an instructions file published in the GitHub repository dipseth/google_workspace_fastmcp2 (25 stars, last pushed today), licensed Apache-2.0. It adds 616 tokens to every session, about $0.0031 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
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.