gws-gmail-reply

A Gmail command for replying to an existing email while keeping the reply in the same conversation thread.

In plain words
What is it for?
Use it to reply with plain text or HTML, add recipients or attachments, save a draft, or preview the request without sending it.
Why use it?
It removes the need to handle Gmail's reply details manually and helps keep the response attached to the correct message.

Skill for Claude CodeCodex

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/streakyc/googleworkspacecli/gws-gmail-reply
Any agent
npx skills add StreakYC/googleworkspacecli --skill gws-gmail-reply
Clone the repo
git clone --depth 1 https://github.com/StreakYC/googleworkspacecli

Made for: Claude Code, Codex.

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 954 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod 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 $0.00019 $0.00954
Opus 5 $0.00010 $0.00477
Sonnet 5 $0.00004 $0.00191
Haiku 4.5 $0.00002 $0.00095

Measured 2d ago against content hash a4c046cd19f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gws-gmail-reply 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 2d 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

This is a copy

92% identical to gws-gmail-reply — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/gws-gmail-reply/SKILL.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

gmail +reply

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

Reply to a message (handles threading automatically)

Usage

gws gmail +reply --message-id <ID> --body <TEXT>

Flags

Flag Required Default Description
--message-id Gmail message ID to reply to
--body Reply body, used verbatim (plain text, or HTML with --html). \n is NOT a newline — use $'...' or a real line break
--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

Examples

gws gmail +reply --message-id 18f1a2b3c4d --body 'Thanks, got it!'
gws gmail +reply --message-id 18f1a2b3c4d --body 'Looping in Carol' --cc [email protected]
gws gmail +reply --message-id 18f1a2b3c4d --body 'Adding Dave' --to [email protected]
gws gmail +reply --message-id 18f1a2b3c4d --body '<b>Bold reply</b>' --html
gws gmail +reply --message-id 18f1a2b3c4d --body 'Updated version' -a updated.docx
gws gmail +reply --message-id 18f1a2b3c4d --body 'Draft reply' --draft
# Multi-line body — $'...' quoting turns \n into a real newline:
gws gmail +reply --message-id 18f1a2b3c4d --body $'Hi John,\n\nConfirmed for Tuesday.\n\nBlake'
# Long body — read it from a file instead of quoting inline:
gws gmail +reply --message-id 18f1a2b3c4d --body "$(cat reply.txt)"

Tips

  • IMPORTANT: --body is verbatim. Writing --body "Hi,\n\nThanks" sends a literal backslash-n to the recipient; it does NOT create a line break. Use $'Hi,\n\nThanks' or "$(cat file.txt)". See gws-shared Shell Tips.
  • Automatically sets In-Reply-To, References, and threadId headers.
  • Quotes the original message in the reply body.
  • --to adds extra recipients to the To field.
  • 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.
  • For reply-all, use +reply-all instead.

Read the full file on GitHub · 72 lines

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. 2d ago First seen · 72 lines · 19 tokens per session scan A a4c046cd19f7

Subscribe to this mod's changes

gws-gmail-reply is a skill published in the GitHub repository StreakYC/googleworkspacecli (0 stars, last pushed 28d ago), licensed Apache-2.0. It adds 19 tokens to every session and 954 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to gws-gmail-reply, differing in 7 lines, and is treated as a copy.

Related

Other skills, from other repositories

hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

nexu-io/open-design · 62 tokens

lark-im

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。.

larksuite/cli · 140 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

reflect

Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.

alvinunreal/oh-my-opencode-slim · 53 tokens

mochi-remind

Handle due reminders — notify the user with natural language and mark them done.

kirodotdev/KiroCrew · 20 tokens

organize-threads

猫猫辅助整理未分类 thread,分析标题和元数据,建议合适的标签。 Use when: 用户说"帮我整理"、"分类 thread"、点击整理按钮。 Not for: 删除/编辑标签本身。 Output: 按 thread 的标签建议列表。.

zts212653/clowder-ai · 65 tokens