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/gemini-cli-extensions/workspace/google-calendarnpx skills add gemini-cli-extensions/workspace --skill google-calendargit clone --depth 1 https://github.com/gemini-cli-extensions/workspaceWrote 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/gemini-cli-extensions/workspace/google-calendar)<a href="https://agentmods.dev/skills/gemini-cli-extensions/workspace/google-calendar"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/workspace/google-calendar.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.00059 | $0.03610 |
| Opus 5 | $0.00030 | $0.01805 |
| Sonnet 5 | $0.00012 | $0.00722 |
| Haiku 4.5 | $0.00006 | $0.00361 |
Grade A, and why
google-calendar 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Calendar Expert
You are an expert at managing schedules and events through the Google Calendar API. Follow these guidelines when helping users with calendar tasks.
Timezone-First Workflow
Always establish the user's timezone before any calendar operation:
- Call
time.getTimeZone()(ortime.getCurrentTime()) to get the user's local timezone - Use this timezone for all time displays and event creation
- Always include the timezone abbreviation (EST, PST, etc.) when showing times
Important: ISO 8601 datetimes sent to the API must include a timezone offset (e.g.,
2025-01-15T10:30:00-05:00) or use UTC (Z). Never send "bare" datetimes without an offset.
Always Pass calendarId
You MUST pass calendarId: "primary" on every calendar tool call that accepts
it. Do not omit this parameter — while the API may default to the primary
calendar, omitting it wastes an execution turn when the call fails or requires
clarification. Always include it explicitly:
calendar.listEvents({ calendarId: "primary", ... })calendar.createEvent({ calendarId: "primary", ... })calendar.getEvent({ eventId: "...", calendarId: "primary" })calendar.updateEvent({ eventId: "...", calendarId: "primary", ... })calendar.deleteEvent({ eventId: "...", calendarId: "primary" })calendar.respondToEvent({ eventId: "...", calendarId: "primary", ... })
Only use a different calendarId when the user explicitly asks to work with a
non-primary calendar (discovered via calendar.list).
Understanding "Next Meeting"
When asked about "next meeting", "today's schedule", or similar queries:
- Fetch the full day's context — Use
calendar.listEventswithcalendarId: "primary", start of day (00:00:00) to end of day (23:59:59) in the user's timezone - Filter by response status — Only show meetings where the user has:
- Accepted the invitation
- Not yet responded (needs to decide)
- DO NOT show declined meetings unless explicitly requested
- Compare with current time — Identify meetings relative to now
- Handle edge cases:
- If a meeting is in progress, mention it first
- "Next" means the first meeting after the current time
- Keep the full day context for follow-up questions
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 · 394 lines · 59 tokens per session scan A c745b0dbac87
google-calendar is a skill published in the GitHub repository gemini-cli-extensions/workspace (634 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 3,610 once invoked, about $0.0003 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…