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 rules/maccman/growth-agents/google-workspacegit clone --depth 1 https://github.com/maccman/growth-agentsWhat 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.00745 | $0.00745 |
| Opus 5 | $0.00373 | $0.00373 |
| Sonnet 5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
google-workspace 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 3d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Workspace (Gmail, Calendar, Drive, etc.)
One-off lookups — use the gws CLI
For quick, one-off tasks against Gmail, Calendar, Drive, Tasks, Contacts, Sheets, or Docs, use the gws CLI directly. No scripting needed.
First verify it's available:
gws --version
If not installed, tell the user to open Terminal (not Cursor) and run the Setup Google Workspace command — gws auth setup is interactive and requires a real terminal.
# Gmail
gws gmail users messages list --params '{"userId": "me", "maxResults": 10, "q": "from:[email protected] newer_than:7d"}'
gws gmail users messages list --params '{"userId": "me", "maxResults": 10, "q": "is:unread subject:invoice"}'
# Calendar
gws calendar events list --params '{"calendarId": "primary", "timeMin": "'$(date -u +%Y-%m-%dT00:00:00Z)'", "maxResults": 50}'
gws calendar events list --params '{"calendarId": "primary", "maxResults": 50}'
# Drive
gws drive files list --params '{"q": "name contains '\''Q4 report'\''", "pageSize": 10}'
gws drive files get --params '{"fileId": "<fileId>", "alt": "media"}' > ./file.pdf
# Tasks / Contacts / Sheets
gws tasks tasklists list
gws people connections list --params '{"resourceName": "people/me", "personFields": "names,emailAddresses"}'
gws sheets spreadsheets values get --params '{"spreadsheetId": "<spreadsheetId>", "range": "Sheet1!A1:D20"}'
All gws output is structured JSON by default.
Programmatic scripts — use the googleapis TypeScript SDK
For anything more than a one-off (looping, writing files, combining APIs, reports), write a TypeScript script. Credentials are already in .env.
import { config } from 'dotenv'
import { google } from 'googleapis'
config()
const oauth2Client = new google.auth.OAuth2(
process.env.GOOGLE_CLIENT_ID,
process.env.GOOGLE_CLIENT_SECRET,
process.env.GOOGLE_REDIRECT_URI,
)
oauth2Client.setCredentials({
access_token: process.env.GOOGLE_ACCESS_TOKEN,
refresh_token: process.env.GOOGLE_REFRESH_TOKEN,
expiry_date: process.env.GOOGLE_TOKEN_EXPIRY ? parseInt(process.env.GOOGLE_TOKEN_EXPIRY) : undefined,
})
const gmail = google.gmail({ version: 'v1', auth: oauth2Client })
const calendar = google.calendar({ version: 'v3', auth: oauth2Client })
const drive = google.drive({ version: 'v3', auth: oauth2Client })
const sheets = google.sheets({ version: 'v4', auth: oauth2Client })
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.
- 3d ago First seen · 75 lines · 745 tokens per session scan A fa9e50879aa9
google-workspace is a cursor rule published in the GitHub repository maccman/growth-agents (5 stars, last pushed 6mo ago), licensed MIT. It adds 745 tokens to every session, about $0.0037 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.