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/googleworkspace/cli/gws-calendar-insertnpx skills add googleworkspace/cli --skill gws-calendar-insertgit clone --depth 1 https://github.com/googleworkspace/cliWhat 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.00014 | $0.00549 |
| Opus 5 | $0.00007 | $0.00275 |
| Sonnet 5 | $0.00003 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
gws-calendar-insert 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- gws-calendar-insert — 100% identical, 0 lines differ
- gws-calendar-insert — 100% identical, 0 lines differ
- gws-calendar-insert — 100% identical, 0 lines differ
- gws-calendar-insert — 89% identical, 9 lines differ
- gws-calendar-insert — 89% identical, 9 lines differ
- gws-calendar-insert — 84% identical, 7 lines differ
What it actually says
calendar +insert
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
create a new event
Usage
gws calendar +insert --summary <TEXT> --start <TIME> --end <TIME>
Flags
| Flag | Required | Default | Description |
|---|---|---|---|
--calendar |
— | primary | Calendar ID (default: primary) |
--summary |
✓ | — | Event summary/title |
--start |
✓ | — | Start time (ISO 8601, e.g., 2024-01-01T10:00:00Z) |
--end |
✓ | — | End time (ISO 8601) |
--location |
— | — | Event location |
--description |
— | — | Event description/body |
--attendee |
— | — | Attendee email (can be used multiple times) |
--meet |
— | — | Add a Google Meet video conference link |
Examples
gws calendar +insert --summary 'Standup' --start '2026-06-17T09:00:00-07:00' --end '2026-06-17T09:30:00-07:00'
gws calendar +insert --summary 'Review' --start ... --end ... --attendee [email protected]
gws calendar +insert --summary 'Meet' --start ... --end ... --meet
Tips
- Use RFC3339 format for times (e.g. 2026-06-17T09:00:00-07:00).
- The --meet flag automatically adds a Google Meet link to the event.
[!CAUTION] This is a write command — confirm with the user before executing.
See Also
- gws-shared — Global flags and auth
- gws-calendar — All manage calendars and events commands
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 · 59 lines · 14 tokens per session scan A 5c54f18a615b
gws-calendar-insert is a skill published in the GitHub repository googleworkspace/cli (30,691 stars, last pushed 7d ago), licensed Apache-2.0. It adds 14 tokens to every session and 549 once invoked, about $0.0001 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
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"…
configure
Step-by-step setup wizard for the GWS connector. Walks through creating a GCP project, getting OAuth credentials, and connecting accounts.
reauth
Re-authorize a connected GWS account to refresh tokens or pick up new OAuth scopes without changing account settings.
add-account
Connect a new Google account to the GWS connector with a custom label. Supports per-account OAuth credentials for different organizations.
remove-account
Disconnect a Google account from the GWS connector and delete its tokens.
set-default
Set the default GWS account used when no account is specified.