nanoclaw-gws-ea: Skill for Claude Code

.claude/skills/add-gmail-tool/SKILL.md

add-gmail-tool is a skill for Claude Code from taslim/nanoclaw-gws-ea. It costs 63 tokens per session (3,739 once invoked), scanned D, original, MIT.

A Gmail connection that gives the agent tools to search, read, draft, send, label, and manage email. Gmail is Google’s email service.

In plain words
What is it for?
It connects Gmail to selected agent groups through OneCLI-managed authentication and exposes email and attachment operations.
Why use it?
It lets the agent work with email while keeping real OAuth credentials—the tokens that grant account access—outside the container.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is taslim/nanoclaw-gws-ea's own configuration. It tells Claude Code how to work on nanoclaw-gws-ea itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything nanoclaw-gws-ea configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./container/build.sh.

Reuse

Borrowing it

Nothing to install: this file belongs to taslim/nanoclaw-gws-ea. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/taslim/nanoclaw-gws-ea/main/.claude/skills/add-gmail-tool/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/taslim/nanoclaw-gws-ea

Made for: Claude Code.

Wrote 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.

agentmods badge for add-gmail-tool

README.md
[![agentmods](https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/add-gmail-tool/github.svg)](https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/add-gmail-tool)
Your own site
<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/add-gmail-tool"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/add-gmail-tool/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.

agentmods 80×15 button for add-gmail-tool

Your own site · 80×15
<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/add-gmail-tool"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/add-gmail-tool.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,739 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.1 $0.00063 $0.03739
Opus 5 $0.00032 $0.01869
Sonnet 5 $0.00013 $0.00748
Haiku 4.5 $0.00006 $0.00374

Measured 11d ago against content hash b04465fda28d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade D, and why

add-gmail-tool scanned grade D with 2 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 11d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

chmod 600 ~/.gmail-mcp/gcp-oauth.keys.json ~/.gmail-mcp/credentials.json

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

5. (Optional) `rm -rf ~/.gmail-mcp/` if no other host-side tool needs the stubs.
.claude/skills/add-gmail-tool/SKILL.md · 263 lines

How it starts

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

Add Gmail Tool (OneCLI-native)

This skill wires the @gongrzhe/server-gmail-autoauth-mcp stdio MCP server into selected agent groups. The MCP server reads stub credentials containing the onecli-managed placeholder; the OneCLI gateway intercepts outbound calls to gmail.googleapis.com and injects the real OAuth bearer from its vault.

Tools exposed (from [email protected], surfaced to the agent as mcp__gmail__<name>): search_emails, read_email, send_email, draft_email, delete_email, modify_email, batch_modify_emails, batch_delete_emails, download_attachment, list_email_labels, create_label, update_label, delete_label, get_or_create_label, list_filters, get_filter, create_filter, create_filter_from_template, delete_filter.

Why this pattern: v2's invariant is that containers never receive raw API keys — OneCLI is the sole credential path (see CHANGELOG v2.0.0). The stub-file pattern satisfies this: the container sees "onecli-managed" placeholders, the gateway swaps them in flight.

Phase 1: Pre-flight

Verify OneCLI has Gmail connected

onecli apps get --provider gmail

Expected: "connection": { "status": "connected" } with scopes including gmail.readonly, gmail.modify, gmail.send.

If not connected, tell the user:

Open the OneCLI web UI at http://127.0.0.1:10254, go to Apps → Gmail, and click Connect. Sign in with the Google account you want the agent to act as.

Verify stub credentials exist

ls -la ~/.gmail-mcp/gcp-oauth.keys.json ~/.gmail-mcp/credentials.json 2>&1

If both exist and contain "onecli-managed":

grep -l onecli-managed ~/.gmail-mcp/gcp-oauth.keys.json ~/.gmail-mcp/credentials.json

...skip to Phase 2.

If either file exists but does not contain onecli-managed, STOP and tell the user — these are real OAuth credentials from a previous non-OneCLI install. Back them up, then delete before proceeding. The OneCLI migration normally handles this; if it didn't, something is wrong.

Read the full file on GitHub · 263 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. 11d ago First seen · 263 lines · 63 tokens per session scan D b04465fda28d

Subscribe to this mod's changes

add-gmail-tool is a skill published in the GitHub repository taslim/nanoclaw-gws-ea (11 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 3,739 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.