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.
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 skills add googleworkspace/cli --skill recipe-create-events-from-sheetgit clone --depth 1 https://github.com/googleworkspace/cliWrote 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/googleworkspace/cli/recipe-create-events-from-sheet)<a href="https://agentmods.dev/skills/googleworkspace/cli/recipe-create-events-from-sheet"><img src="https://agentmods.dev/badge/skills/googleworkspace/cli/recipe-create-events-from-sheet.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.1 | $0.00023 | $0.00242 |
| Opus 5 | $0.00012 | $0.00121 |
| Sonnet 5 | $0.00005 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
recipe-create-events-from-sheet 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
3 near-identical copies found in the catalogue:
- recipe-create-events-from-sheet — 100% identical, 0 lines differ
- recipe-create-events-from-sheet — 100% identical, 0 lines differ
- recipe-create-events-from-sheet — 100% identical, 0 lines differ
What it actually says
Create Google Calendar Events from a Sheet
PREREQUISITE: Load the following skills to execute this recipe:
gws-sheets,gws-calendar
Read event data from a Google Sheets spreadsheet and create Google Calendar entries for each row.
Steps
- Read event data:
gws sheets +read --spreadsheet SHEET_ID --range "Events!A2:D" - For each row, create a calendar event:
gws calendar +insert --summary 'Team Standup' --start '2026-01-20T09:00:00' --end '2026-01-20T09:30:00' --attendee [email protected] --attendee [email protected]
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 · 28 lines · 23 tokens per session scan A 855ab91cbef7
recipe-create-events-from-sheet is a skill published in the GitHub repository googleworkspace/cli (30,753 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 242 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-09-03.
Other skills, from other repositories
atmos-migration
This skill helps you migrate a repository to Atmos. It covers native Terraform, Terraform Workspaces, Terramate, Terragrunt, Makefiles, Justfiles, and Taskfiles. It gives minimum-disruption paths, file-layout options, workspace mapping, task-to-command mapping, generatehcl/script decomposition, and the remote-state…
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-init
Bootstrapping new Atmos projects with atmos init: built-in template catalog, differences from atmos scaffold generate, project record, and update-safe 3-way merge.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
atmos-imports
Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts.
swarm-plan
Full execution protocol for MODE: PLAN -- plan creation, external plan ingestion, QA gate persistence, task granularity, and traceability checks.