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 commands/maccman/growth-agents/setup-google-workspacegit clone --depth 1 https://github.com/maccman/growth-agentsWrote 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/commands/maccman/growth-agents/setup-google-workspace)<a href="https://agentmods.dev/commands/maccman/growth-agents/setup-google-workspace"><img src="https://agentmods.dev/badge/commands/maccman/growth-agents/setup-google-workspace.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.00000 | $0.03098 |
| Opus 5 | $0.00000 | $0.01549 |
| Sonnet 5 | $0.00000 | $0.00620 |
| Haiku 4.5 | $0.00000 | $0.00310 |
Grade C, and why
setup-google-workspace scanned grade C with 2 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
### 5c — Extract credentials to .env Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
import { exec } from 'child_process' How it starts
The opening of the file, as written. The whole thing — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Google Workspace
This command sets up Google Workspace API access by installing the gws CLI and the googleapis npm package for TypeScript agent scripts.
Steps 1-4 MUST be run by the user in a real Terminal window, NOT from inside Cursor. The
gwsauth flow is highly interactive (opens browsers, requires terminal input) and cannot be automated.
Step 1 — Install gws
Tell the user to open Terminal and run:
npm install -g @googleworkspace/cli
Verify:
gws --version
Step 2 — Run gws auth setup
This step is interactive and MUST be done in Terminal, not from Cursor.
If gcloud is installed:
Tell the user to run:
gws auth setup
This single command handles everything:
- Creates a GCP project
- Enables required APIs
- Configures OAuth consent screen
- Logs you in via browser
If gcloud is NOT installed:
Two options:
- Install gcloud first —
brew install --cask google-cloud-sdk, then rungws auth setupas above. - Manual path — Create a project in Cloud Console, configure OAuth consent screen, create a Desktop OAuth client, download the client JSON to
~/.config/gws/client_secret.json, then run:gws auth login
Credentials are stored encrypted in the OS keychain (~/.config/gws/).
Step 3 — Scope warning
Unverified apps (testing mode) are limited to ~25 OAuth scopes. Instead of accepting the broad default scope set, use the --scopes flag to request only what you need:
gws auth login --scopes drive,gmail,calendar
Tell the user to keep their scope list minimal to stay under the limit.
Step 4 — Verify gws
Smoke-test in Terminal:
gws gmail users messages list --params '{"userId": "me", "maxResults": 5}'
gws calendar events list --params '{"calendarId": "primary"}'
Expected: JSON output with email message IDs and calendar events.
Troubleshooting:
- Auth issues — re-run
gws auth login permission denied/403— an API isn't enabled; re-rungws auth setupor enable manually in Cloud Consoleaccount not added as test user— add your email under OAuth consent screen > Test Users in Cloud Console
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 · 414 lines · 0 tokens per session scan C 81124bb48012
setup-google-workspace is a command published in the GitHub repository maccman/growth-agents (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,098 tokens. A static security scan graded it C with 2 findings (harvests environment variables, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.