gws-setup

gws-setup is a skill for Claude Code from metraton/gaia. It costs 22 tokens per session (1,392 once invoked), scanned A, original, MIT.

A setup procedure for the Google Workspace command-line tool, which lets terminal commands work with Google services such as Gmail and Drive.

In plain words
What is it for?
Use it when installing or configuring the gws command for a Google account.
Why use it?
It guides account authentication and Google Cloud setup through steps that can differ between personal and work accounts. This helps avoid configuration failures involving accounts and permissions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the gaia plugin — 38 skills, 9 agents, 11 hooks shipped together

Good fit Use it when installing or configuring the gws command for a Google…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/metraton/gaia/gws-setup
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.

Any agent
npx skills add metraton/gaia --skill gws-setup
Clone the repo
git clone --depth 1 https://github.com/metraton/gaia

Made for: Claude Code.

Or install gaia, the plugin that ships this one along with the rest of its 38 skills, 9 agents, 11 hooks.

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 gws-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/metraton/gaia/gws-setup.svg)](https://agentmods.dev/skills/metraton/gaia/gws-setup)
Your own site
<a href="https://agentmods.dev/skills/metraton/gaia/gws-setup"><img src="https://agentmods.dev/badge/skills/metraton/gaia/gws-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,392 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00022 $0.01392
Opus 5 $0.00011 $0.00696
Sonnet 5 $0.00004 $0.00278
Haiku 4.5 $0.00002 $0.00139

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

Security

Grade A, and why

gws-setup 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 6d 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.

skills/gws-setup/SKILL.md · 106 lines

How it starts

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

GWS Setup

The gws CLI looks straightforward but breaks in subtle ways -- Google's OAuth flow has undocumented constraints that differ between personal and organizational accounts, and the gws tool itself has open bugs around scopes and multi-account. This procedure captures the working path and the traps discovered through real setup sessions, so you avoid the silent failures that waste hours.

Prerequisites: gcloud CLI installed, browser access for OAuth, interactive terminal for auth steps.

Procedure

1. Install gws binary

2. Add Google account to gcloud

  • gcloud auth login <email> --no-launch-browser (interactive terminal required)
  • This adds alongside existing accounts -- does NOT replace them
  • After login, restore work account: gcloud config set account <work-account>

3. Create or select GCP project

  • Check existing: gcloud projects list --account=<email>
  • Create new: gcloud projects create gaia-<name> --name="Gaia <Name>" --account=<email>
  • Naming: gaia-<identifier>-personal or gaia-<identifier>-work

4. gws auth setup

  • gws auth setup --project <project-id>
  • TRAP: When selecting scopes, DO NOT use presets ("Recommended" or "Read Only") -- they include organizational scopes that break for @gmail.com accounts

5. Scope selection (CRITICAL)

For safe scopes and blocked scopes by account type, read reference.md in this directory.

Known bug: gws issue #119 -- gws auth login unusable with personal @gmail.com when organizational scopes are included. Google returns 400: invalid_scope.

6. OAuth consent screen (manual in browser)

  • URL: https://console.cloud.google.com/apis/credentials/consent?project=<project-id>
  • User Type: External | App name: gws CLI | Support email: the account email
  • TRAP: Add the account as a Test User BEFORE attempting login
    • Test Users section -> Add Users -> enter the email
    • Without this, Google returns 403: access_denied ("app not verified")

Read the full file on GitHub · 106 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 6d ago First seen · 106 lines · 22 tokens per session scan A 0fc55c4a3691

Subscribe to this mod's changes

gws-setup is a skill published in the GitHub repository metraton/gaia (3 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 1,392 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.