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 agentmods add skills/streakyc/googleworkspacecli/gws-gmail-reply-allnpx skills add StreakYC/googleworkspacecli --skill gws-gmail-reply-allgit clone --depth 1 https://github.com/StreakYC/googleworkspacecliWrote 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/streakyc/googleworkspacecli/gws-gmail-reply-all)<a href="https://agentmods.dev/skills/streakyc/googleworkspacecli/gws-gmail-reply-all"><img src="https://agentmods.dev/badge/skills/streakyc/googleworkspacecli/gws-gmail-reply-all.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 | $0.00021 | $0.01024 |
| Opus 5 | $0.00010 | $0.00512 |
| Sonnet 5 | $0.00004 | $0.00205 |
| Haiku 4.5 | $0.00002 | $0.00102 |
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 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.
This is a copy
92% identical to gws-gmail-reply-all — 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.
How it starts
The opening of the file, as written. The whole thing — 75 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, 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 |
--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
# Multi-line body — $'...' quoting turns \n into a real newline:
gws gmail +reply-all --message-id 18f1a2b3c4d --body $'Hi all,\n\nConfirmed for Tuesday.\n\nBlake'
# Long body — read it from a file instead of quoting inline:
gws gmail +reply-all --message-id 18f1a2b3c4d --body "$(cat reply.txt)"
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 · 75 lines · 21 tokens per session scan A 86035c12098a
gws-gmail-reply-all is a skill published in the GitHub repository StreakYC/googleworkspacecli (0 stars, last pushed 29d ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,024 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-all, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…