Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Elnora-AI/elnora-google-workspace/plugin install google-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/elnora-ai/elnora-google-workspace/gw-calendar)<a href="https://agentmods.dev/skills/elnora-ai/elnora-google-workspace/gw-calendar"><img src="https://agentmods.dev/badge/skills/elnora-ai/elnora-google-workspace/gw-calendar/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/elnora-ai/elnora-google-workspace/gw-calendar"><img src="https://agentmods.dev/badge/skills/elnora-ai/elnora-google-workspace/gw-calendar.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00130 | $0.02603 |
| Opus 5 | $0.00065 | $0.01301 |
| Sonnet 5 | $0.00026 | $0.00521 |
| Haiku 4.5 | $0.00013 | $0.00260 |
Grade A, and why
gw-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 11d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calendar
Account
Events are created on the default account unless you pass --account <name>. The default account is configurable — run gw auth list to see the accounts you have set up, and pass --account <name> to target a specific one.
Required Fields — always populate
Every create and update MUST include ALL of these fields. Never create a partial event.
| Field | Flag | Default |
|---|---|---|
| Title | --title |
— (required) |
| Start time | --start |
— (required) |
| Duration | --duration |
30 min |
| Description | --description |
— |
| Location | --location |
— |
| Attendees | --attendees |
— |
| Reminders | --reminders |
60,30,10 (auto) |
| Meet link | --meet |
only when virtual |
If the request is missing any of these details:
- Search email first. Use the gmail skill to find the relevant thread:
Extract: location/address, attendees, agenda/description, time details.$CLI gmail list --query "subject:KEYWORD" --limit 5 --compact $CLI gmail get MESSAGE_ID --compact - If email doesn't have it, ask the user. Do not guess or leave fields blank.
Examples of what to look for:
- "Let's meet at the office" → search email for the address, use as
--location. - "Call with Alex" → search email for Alex's email, full name for title, any agenda for description.
- "Coffee with investor" → search email for venue name + address, attendee email.
- In-person →
--locationwith full address. Virtual →--meetflag. Hybrid → both. - Workspace may auto-attach a Meet link on any event write (account "Automatically add Google Meet" setting), so an in-person event can sprout one after an unrelated
update. That's not a bug. Pass--meet falseto strip it (the CLI sendsconferenceDataVersion=1, required for removal to take effect).
Defaults (auto-applied)
- Reminders: 60, 30, 10 min popup — set automatically on
create. Do NOT change unless the user explicitly requests different reminders. Override:--reminders "120,15". - Duration: 30 minutes.
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.
- 11d ago First seen · 191 lines · 130 tokens per session scan A 42b7f34cd0f3
gw-calendar is a skill published in the GitHub repository Elnora-AI/elnora-google-workspace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 130 tokens to every session and 2,603 once invoked, about $0.0006 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 skills, from other repositories
managing-google-workspace
Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search). Supports MCP tools or CLI via uvx workspace-mcp --cli. Provides tool routing, workflows, and parameter guidance for 114 tools. Triggers for "check my email"…
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
alive-cleanup
System maintenance -- stale tasks, orphan folders, unsaved sessions, world health check.