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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/googleworkspace/clinpx agentmods add skills/googleworkspace/cli/gws-peopleWrote 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/gws-people)<a href="https://agentmods.dev/skills/googleworkspace/cli/gws-people"><img src="https://agentmods.dev/badge/skills/googleworkspace/cli/gws-people/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/googleworkspace/cli/gws-people"><img src="https://agentmods.dev/badge/skills/googleworkspace/cli/gws-people.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00013 | $0.01393 |
| Opus 5.5 | $0.00005 | $0.00557 |
| Sonnet 5.5 | $0.00003 | $0.00279 |
| Haiku 4.5 | $0.00001 | $0.00139 |
Grade A, and why
gws-people 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 1mo 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
5 near-identical copies found in the catalogue:
- gws-people — 100% identical, 0 lines differ
- gws-people — 100% identical, 0 lines differ
- gws-people — 100% identical, 5 lines differ
- gws-people — 100% identical, 0 lines differ
- gws-people — 98% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
people (v1)
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws people <resource> <method> [flags]
API Resources
contactGroups
batchGet— Get a list of contact groups owned by the authenticated user by specifying a list of contact group resource names.create— Create a new contact group owned by the authenticated user. Created contact group names must be unique to the users contact groups. Attempting to create a group with a duplicate name will return a HTTP 409 error. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.delete— Delete an existing contact group owned by the authenticated user by specifying a contact group resource name. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.get— Get a specific contact group owned by the authenticated user by specifying a contact group resource name.list— List all contact groups owned by the authenticated user. Members of the contact groups are not populated.update— Update the name of an existing contact group owned by the authenticated user. Updated contact group names must be unique to the users contact groups. Attempting to create a group with a duplicate name will return a HTTP 409 error. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.members— Operations on the 'members' resource
otherContacts
copyOtherContactToMyContactsGroup— Copies an "Other contact" to a new contact in the user's "myContacts" group Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.list— List all "Other contacts", that is contacts that are not in a contact group. "Other contacts" are typically auto created contacts from interactions. Sync tokens expire 7 days after the full sync. A request with an expired sync token will get an error with an google.rpc.ErrorInfo with reason "EXPIRED_SYNC_TOKEN". In the case of such an error clients should make a full sync request without async_token.search— Provides a list of contacts in the authenticated user's other contacts that matches the search query. The query matches on a contact'snames,emailAddresses, andphoneNumbersfields that are from the OTHER_CONTACT source. IMPORTANT: Before searching, clients should send a warmup request with an empty query to update the cache. See https://developers.google.com/people/v1/other-contacts#search_the_users_other_contacts
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.
- 1mo ago First seen · 69 lines · 13 tokens per session scan A 76fe674c72c6
gws-people is a skill published in the GitHub repository googleworkspace/cli (31,821 stars, last pushed 17d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,393 once invoked, about $0.0001 per session on Opus 5.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
gum
Use when an agent needs Google API discovery, gum CLI calls, OAuth setup, or catalog-backed workflows.
gum-hasp
Use when a gum workflow needs local secrets protected by HASP.
gum-mcp
Use when an agent needs to wire or drive gum MCP tools for guarded Google API work.
gws-cli
Use the Google Workspace CLI to inspect schemas, authenticate safely, and run Google Workspace API commands. Use when the user wants to work with Drive, Gmail, Sheets, Docs, Calendar, Chat, Tasks, or other Google Workspace APIs through the gws command.
nlm-skill
Expert guide for the NotebookLM CLI (nlm) and MCP server - interfaces for Google NotebookLM. Use this skill when users want to interact with NotebookLM programmatically, including: creating/managing notebooks, adding sources (URLs, YouTube, text, Google Drive), generating content (podcasts, reports, quizzes…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.