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 skills/burkeholland/max/gogclinpx skills add burkeholland/max --skill gogcligit clone --depth 1 https://github.com/burkeholland/maxWrote 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/skills/burkeholland/max/gogcli)<a href="https://agentmods.dev/skills/burkeholland/max/gogcli"><img src="https://agentmods.dev/badge/skills/burkeholland/max/gogcli.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.00048 | $0.01268 |
| Opus 5 | $0.00024 | $0.00634 |
| Sonnet 5 | $0.00010 | $0.00254 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
Google (gogcli) 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 5d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google CLI (gogcli)
Max can interact with Google services using the gog CLI tool. This covers Gmail, Calendar, Drive, Contacts, Tasks, Sheets, Docs, Slides, Forms, and more.
Prerequisites
gogmust be installed:brew install steipete/tap/gogcli- OAuth credentials must be stored:
gog auth credentials ~/path/to/client_secret.json - User must be authenticated:
gog auth add [email protected] - Check auth status:
gog auth status
If gog is not installed or not authenticated, guide the user through setup.
Important Flags
Always use these flags when running gog commands programmatically:
--jsonor-j— JSON output (best for parsing results)--plainor-p— stable TSV output (good for simple lists)--no-input— never prompt for input (prevents hanging)--forceor-y— skip confirmations for destructive commands-a [email protected]— specify which Google account to use
Gmail
# Search emails (Gmail query syntax)
gog gmail search "is:unread" --json
gog gmail search "from:[email protected]" --json
gog gmail search "subject:meeting is:unread newer_than:1d" --json
# Read a specific message
gog gmail get <messageId> --json
# Send an email
gog send --to "[email protected]" --subject "Hello" --body "Message body"
gog send --to "[email protected]" --cc "[email protected]" --subject "Hi" --body "Hello" --html
# Reply to a thread
gog gmail messages reply <messageId> --body "Reply text"
# List labels
gog gmail labels list --json
# Manage threads
gog gmail thread get <threadId> --json
gog gmail thread modify <threadId> --add-labels "STARRED"
gog gmail thread modify <threadId> --remove-labels "UNREAD"
# Drafts
gog gmail drafts list --json
gog gmail drafts create --to "[email protected]" --subject "Draft" --body "Content"
Calendar
# List today's events
gog calendar events --json
# List events in a date range
gog calendar events --from "2025-01-01" --to "2025-01-31" --json
# List all calendars
gog calendar calendars --json
# Create an event
gog calendar create <calendarId> --summary "Meeting" --start "2025-01-15T10:00:00" --end "2025-01-15T11:00:00"
# Search events
gog calendar search "standup" --json
# Find conflicts
gog calendar conflicts --json
# RSVP to an event
gog calendar respond <calendarId> <eventId> --status accepted
# Free/busy check
gog calendar freebusy "[email protected]" --from "2025-01-15" --to "2025-01-16" --json
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 169 lines · 48 tokens per session scan A 13c1bfc830ed
Google (gogcli) is a skill published in the GitHub repository burkeholland/max (140 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 1,268 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…