recipe-batch-invite-to-event

recipe-batch-invite-to-event is a skill for Claude Code, Codex from googleworkspace/cli. It costs 23 tokens per session (264 once invoked), scanned A, original, Apache-2.0.

A calendar recipe for adding several people to an existing Google Calendar event and notifying them.

In plain words
What is it for?
Updating an event with a list of attendee email addresses and checking that they were added.
Why use it?
It avoids editing each attendee entry manually and helps ensure invitees receive updates.

Skill for Claude CodeCodex

About the project

gws is a command-line tool that provides one interface to Google Workspace services such as Drive, Gmail, Calendar, Sheets, Docs, Chat, and Admin. People and AI agents use it to automate Workspace tasks and receive structured JSON results, while its commands are generated dynamically from Google's Discovery Service. The catalogue contains skills and instructions for using gws.

googleworkspace/cli · 30,742 stars · on GitHub · developers.google.com

Install

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.

agentmods
npx agentmods add skills/googleworkspace/cli/recipe-batch-invite-to-event
Any agent
npx skills add googleworkspace/cli --skill recipe-batch-invite-to-event
Clone the repo
git clone --depth 1 https://github.com/googleworkspace/cli

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for recipe-batch-invite-to-event

README.md
[![agentmods](https://agentmods.dev/badge/skills/googleworkspace/cli/recipe-batch-invite-to-event.svg)](https://agentmods.dev/skills/googleworkspace/cli/recipe-batch-invite-to-event)
Your own site
<a href="https://agentmods.dev/skills/googleworkspace/cli/recipe-batch-invite-to-event"><img src="https://agentmods.dev/badge/skills/googleworkspace/cli/recipe-batch-invite-to-event.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 264 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00264
Opus 5 $0.00012 $0.00132
Sonnet 5 $0.00005 $0.00053
Haiku 4.5 $0.00002 $0.00026

Measured 6d ago against content hash 64f1c9736a2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

recipe-batch-invite-to-event 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 6d 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.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

skills/recipe-batch-invite-to-event/SKILL.md · 28 lines

What it actually says

Add Multiple Attendees to a Calendar Event

PREREQUISITE: Load the following skills to execute this recipe: gws-calendar

Add a list of attendees to an existing Google Calendar event and send notifications.

Steps

  1. Get the event: gws calendar events get --params '{"calendarId": "primary", "eventId": "EVENT_ID"}'
  2. Add attendees: gws calendar events patch --params '{"calendarId": "primary", "eventId": "EVENT_ID", "sendUpdates": "all"}' --json '{"attendees": [{"email": "[email protected]"}, {"email": "[email protected]"}, {"email": "[email protected]"}]}'
  3. Verify attendees: gws calendar events get --params '{"calendarId": "primary", "eventId": "EVENT_ID"}'
Changes

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.

  1. 6d ago First seen · 28 lines · 23 tokens per session scan A 64f1c9736a2f

Subscribe to this mod's changes

recipe-batch-invite-to-event is a skill published in the GitHub repository googleworkspace/cli (30,742 stars, last pushed 10d ago), licensed Apache-2.0. It adds 23 tokens to every session and 264 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.

Related

Other skills, from other repositories

aident-skill

Use Aident Loadout to connect your AI agents to 1,000+ real-world apps and tools like Gmail, Slack, Linear, Notion, Firecrawl, and Fal, unlock 27,000+ executable actions, and track full audit history so your agents can get real work done reliably.

Aident-AI/aident-skill · 66 tokens

save-handoff

Save a concise handoff summary only when the user explicitly requests it. Use this for resumable progress notes in generic agent environments where a real session importer is not guaranteed.

nowledge-co/community · 38 tokens

configure

Step-by-step setup wizard for the GWS connector. Walks through creating a GCP project, getting OAuth credentials, and connecting accounts.

orieg/gws-connector · 30 tokens

building-workflows

Build, edit, test, enable, and monitor PostHog workflows over MCP. Author the action/edge graph so it runs and opens cleanly in the visual editor, then change drafts surgically with patch operations. Use when asked to build, set up, automate, change, fix, or debug a workflow, campaign, broadcast, drip sequence, or…

PostHog/ai-plugin · 85 tokens

skills-store

Discover and use shared team skills stored in PostHog. Use when the user asks to list, browse, load, or manage "shared skills", "team skills", or references the "skills store" / "skill store".

PostHog/ai-plugin · 49 tokens

managing-reminders

Create and manage PostHog reminders — private, human-paced nudges that fire as in-app notifications on a schedule, optionally linked to a PostHog resource. Use when the user says "remind me to…", wants a one-off or recurring nudge (daily/weekly/monthly/yearly, a cron schedule, or a specific date/time), wants to be…

PostHog/ai-plugin · 146 tokens