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-gmail-reply-allWrote 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-gmail-reply-all)<a href="https://agentmods.dev/skills/googleworkspace/cli/gws-gmail-reply-all"><img src="https://agentmods.dev/badge/skills/googleworkspace/cli/gws-gmail-reply-all/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-gmail-reply-all"><img src="https://agentmods.dev/badge/skills/googleworkspace/cli/gws-gmail-reply-all.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- 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.00021 | $0.00847 |
| Opus 5.5 | $0.00008 | $0.00339 |
| Sonnet 5.5 | $0.00004 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
gws-gmail-reply-all 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
6 near-identical copies found in the catalogue:
- gws-gmail-reply-all — 100% identical, 0 lines differ
- gws-gmail-reply-all — 100% identical, 0 lines differ
- gws-gmail-reply-all — 100% identical, 0 lines differ
- gws-gmail-reply-all — 92% identical, 7 lines differ
- gws-gmail-reply-all — 86% identical, 21 lines differ
- gws-gmail-reply-all — 78% identical, 28 lines differ
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gmail +reply-all
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Reply-all to a message (handles threading automatically)
Usage
gws gmail +reply-all --message-id <ID> --body <TEXT>
Flags
| Flag | Required | Default | Description |
|---|---|---|---|
--message-id |
✓ | — | Gmail message ID to reply to |
--body |
✓ | — | Reply body (plain text, or HTML with --html) |
--from |
— | — | Sender address (for send-as/alias; omit to use account default) |
--to |
— | — | Additional To email address(es), comma-separated |
--attach |
— | — | Attach a file (can be specified multiple times) |
--cc |
— | — | CC email address(es), comma-separated |
--bcc |
— | — | BCC email address(es), comma-separated |
--html |
— | — | Treat --body as HTML content (default is plain text) |
--dry-run |
— | — | Show the request that would be sent without executing it |
--draft |
— | — | Save as draft instead of sending |
--remove |
— | — | Exclude recipients from the outgoing reply (comma-separated emails) |
Examples
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Sounds good to me!'
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Updated' --remove [email protected]
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Adding Eve' --cc [email protected]
gws gmail +reply-all --message-id 18f1a2b3c4d --body '<i>Noted</i>' --html
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Notes attached' -a notes.pdf
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Draft reply' --draft
Tips
- Replies to the sender and all original To/CC recipients.
- Use --to to add extra recipients to the To field.
- Use --cc to add new CC recipients.
- Use --bcc for recipients who should not be visible to others.
- Use --remove to exclude recipients from the outgoing reply, including the sender or Reply-To target.
- The command fails if no To recipient remains after exclusions and --to additions.
- Use -a/--attach to add file attachments. Can be specified multiple times.
- With --html, the quoted block uses Gmail's gmail_quote CSS classes and preserves HTML formatting. Use fragment tags (, , , etc.) — no / wrapper needed.
- With --html, inline images in the quoted message are preserved via cid: references.
- Use --draft to save the reply as a draft instead of sending it immediately.
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 · 70 lines · 21 tokens per session scan A 095cee7197b2
gws-gmail-reply-all is a skill published in the GitHub repository googleworkspace/cli (31,694 stars, last pushed 13d ago), licensed Apache-2.0. It adds 21 tokens to every session and 847 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-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.
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
instagram-skill
How to use Instagram CLI to interact with Instagram from the command line on behalf of a user. Use this skill whenever the user wants to send or read Instagram messages, check their inbox, reply to or unsend messages, or automate any Instagram DM workflow via the CLI. This includes tasks phrased as "message X on…