nanoclaw-gws-ea: Skill for Claude Code

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

add-gcal-tool is a skill for Claude Code from taslim/nanoclaw-gws-ea. It costs 67 tokens per session (2,849 once invoked), scanned D, original, MIT.

A Google Calendar connection for listing, searching, creating, updating, and deleting events, including free/busy checks. Google Calendar is Google’s scheduling service.

In plain words
What is it for?
It connects selected agent groups through OneCLI-managed authentication and supports multiple calendars and accounts.
Why use it?
It lets the agent work across calendars without placing real OAuth credentials inside the container.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

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-gcal-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-gcal-tool

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/add-gcal-tool"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/add-gcal-tool.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,849 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.00067 $0.02849
Opus 5 $0.00034 $0.01425
Sonnet 5 $0.00013 $0.00570
Haiku 4.5 $0.00007 $0.00285

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

Security

Grade D, and why

add-gcal-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 12d 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 ~/.calendar-mcp/*.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 ~/.calendar-mcp/` and `onecli apps disconnect --provider google-calendar`.
.claude/skills/add-gcal-tool/SKILL.md · 239 lines

How it starts

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

Add Google Calendar Tool (OneCLI-native)

This skill wires @cocal/google-calendar-mcp into selected agent groups. The MCP server reads stub credentials containing the onecli-managed placeholder; the OneCLI gateway intercepts outbound calls to calendar.googleapis.com / oauth2.googleapis.com and swaps the bearer for the real OAuth token from its vault.

Why this package (and not gongrzhe's): @gongrzhe/server-calendar-autoauth-mcp only supports the primary calendar and exposes 5 tools (no list_calendars). @cocal/google-calendar-mcp explicitly supports multi-calendar and multi-account, and is actively maintained.

Tools exposed (surfaced as mcp__calendar__<name>, exact set depends on version — run tools/list against the MCP server to enumerate): list-calendars, list-events, search-events, create-event, update-event, delete-event, get-event, list-colors, get-freebusy, get-current-time, plus multi-account management tools.

Why this pattern: v2's invariant is that containers never receive raw API keys (CHANGELOG 2.0.0). Same stub pattern /add-gmail-tool uses. This skill is deliberately a sibling, not a combined "Google Workspace" skill — installs independently and removes cleanly.

Phase 1: Pre-flight

Verify OneCLI has Google Calendar connected

onecli apps get --provider google-calendar

Expected: "connection": { "status": "connected" } with scopes including calendar.readonly and calendar.events.

If not connected, tell the user:

Open the OneCLI web UI at http://127.0.0.1:10254, go to Apps → Google Calendar, and click Connect. Sign in with the Google account the agent should act as. calendar.readonly + calendar.events are the minimum useful scopes.

Verify stub credentials exist

The stub lives at ~/.calendar-mcp/ by convention (shared with /add-gmail-tool's sibling). cocal doesn't default to this path (it uses ~/.config/google-calendar-mcp/tokens.json) — we override via env vars below so it reads our stubs instead.

Read the full file on GitHub · 239 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. 12d ago First seen · 239 lines · 67 tokens per session scan D a6a3438fd276

Subscribe to this mod's changes

add-gcal-tool is a skill published in the GitHub repository taslim/nanoclaw-gws-ea (11 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 2,849 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.