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 fakoli/fakoli-plugins --skill gws-gmail-reply-allgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/gws-gmail-reply-all)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/gws-gmail-reply-all"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/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/fakoli/fakoli-plugins/gws-gmail-reply-all"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/gws-gmail-reply-all.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00640 |
| Opus 5 | $0.00010 | $0.00320 |
| Sonnet 5 | $0.00004 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
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 5d 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
78% identical to gws-gmail-reply-all — 28 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gmail +reply-all
Reference: See the
gws-sharedskill for auth, global flags, and security rules.
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 |
--cc |
— | — | Additional CC email address(es), comma-separated |
--bcc |
— | — | BCC email address(es), comma-separated |
--remove |
— | — | Exclude recipients from the outgoing reply (comma-separated emails) |
--html |
— | — | Send as HTML (quotes original with Gmail styling; treat --body as HTML) |
--dry-run |
— | — | Show the request that would be sent without executing it |
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 'Adding Dave' --to [email protected]
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Reply' --bcc [email protected]
gws gmail +reply-all --message-id 18f1a2b3c4d --body '<i>Noted</i>' --html
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.
See Also
- gws-shared — Global flags and auth
- gws-gmail — All send, read, and manage email commands
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.
- 5d ago First seen · 56 lines · 21 tokens per session scan A 2a464c4072bb
gws-gmail-reply-all is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 640 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to gws-gmail-reply-all, differing in 28 lines, and is treated as a copy.
Other skills, from other repositories
fp-yoohoo
Terminal-recall mode. Reference for fp-yoohoo, the plugin that brings the terminal window to the foreground when Claude Code stops and waits on a human: a permission prompt, a question dialog, a plan to approve. Explains what it hooks, which desktops it can raise a window on, how the already-focused guard works, and…
hr-operations
A skill for designing remote-work and team-operation policies. It covers flexible work, asynchronous communication, collaboration tools, productivity tracking, and employee experience.
collab-conflict
A guide for handling difficult workplace colleagues and recurring communication conflicts.
collab-feedback-loop
A guide for giving and receiving workplace feedback about specific actions and their effects.
productivity-retro
A guided review for looking back on a week, month, quarter, or year and choosing what to do next. It uses short formats such as KPT: Keep, Problem, and Try.
go
Execute the ADR-driven 4-phase development workflow (preflight, implementation, formatting, release). Use whenever the user says 'itp go'.