agentmods.dev

add-account

add-account is a skill for Claude Code from orieg/gws-connector. It costs 27 tokens per session (524 once invoked), scanned A, original, MIT.

Instructions for connecting another Google account to a Google Workspace connector and giving it a label such as work, personal, or a client name.

In plain words
What is it for?
They help add an account through Google's OAuth sign-in process, using either a downloaded credentials file or a client ID and secret.
Why use it?
They make it possible to route later Gmail, Calendar, or other Workspace actions to the correct organisation or account.

Skill for Claude Code

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

Part of the gws plugin — 6 skills, 1 agent, 1 hook, 1 MCP server shipped together

not rated 1repo yesterday A scan 27 tokens original MIT

Good fit They help add an account through Google's OAuth sign-in process, using either a downloaded credentials file or a client ID and secret.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orieg/gws-connector/add-account
View source ↗ orieg/gws-connector orieg.github.io
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 orieg/gws-connector --skill add-account
Clone the repo
git clone --depth 1 https://github.com/orieg/gws-connector

Made for: Claude Code.

Or install gws, the plugin that ships this one along with the rest of its 6 skills, 1 agent, 1 hook, 1 MCP server.

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-account

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/orieg/gws-connector/add-account"><img src="https://agentmods.dev/badge/skills/orieg/gws-connector/add-account.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 524 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.00027 $0.00524
Opus 5 $0.00014 $0.00262
Sonnet 5 $0.00005 $0.00105
Haiku 4.5 $0.00003 $0.00052

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

Security

Grade A, and why

add-account 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 10d 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/add-account/SKILL.md · 44 lines

How it starts

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

Add Account

Connect a new Google account via OAuth authorization.

Usage

The user provides a label (e.g., "work", "personal", "client-acme") that will be used to reference this account in all tool calls.

Steps

  1. Ask the user for a label for this account
  2. Ask the user for their OAuth credentials. They can either:
    • Point to a downloaded JSON file: Read the client_secret_*.json file to extract client_id and client_secret from the installed object
    • Provide Client ID and Client Secret directly as text
    • If the user has already connected accounts, ask if this new account uses the same GCP project or a different one. If the same, offer to reuse the existing client ID (the secret is in the keychain; they may need to provide it again or point to the same JSON file).
  3. Call gws.accounts.add with the label, clientId, and clientSecret params. The tool opens the browser and waits up to ~60 seconds for the user to complete consent.
  4. The response is one of:
    • Success → report the connected email and total account count.
    • Error → report and stop.
    • Status: pending (user was slow) → call gws.accounts.complete with the returned pendingId. Repeat until success or error.
  5. The client secret is stored securely in the OS keychain.

Per-account credentials

Each account stores its own OAuth credentials. Different Google Workspace organizations need different GCP OAuth apps. For example:

  • personal account: uses your personal GCP project's credentials
  • work account at Company A: uses Company A's GCP project credentials
  • client-acme account: uses Acme Corp's GCP project credentials

Each org's admin creates their own GCP project with OAuth credentials. See /gws:configure for step-by-step GCP setup.

Notes

  • If no credentials are provided, the tool returns setup instructions (or run /gws:configure)
  • The first account added becomes the default
  • The browser must be accessible for the OAuth flow
  • Client secrets are stored in the OS keychain (macOS Keychain, GNOME Keyring), not in config files

Read the full file on GitHub · 44 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. 10d ago First seen · 44 lines · 27 tokens per session scan A 1cd6068d01e3

Subscribe to this mod's changes

add-account is a skill published in the GitHub repository orieg/gws-connector (1 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 524 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.

claude-code-plugingemini-cli-extensiongoogle-workspacemulti-account
Related

Other skills, from other repositories

domscribe

Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component…

patchorbit/domscribe · 94 tokens

forge-connector

Guides building and deploying Atlassian Forge Teamwork Graph connector apps that ingest external data into Atlassian's Teamwork Graph, making it searchable in Rovo Search and surfaced in Rovo Chat. Use when the user wants to build a Forge connector, ingest external data into Atlassian, connect a third-party tool (e.g.…

atlassian/forge-skills · 121 tokens

forge-cost-optimizer

Optimizes Atlassian Forge apps to reduce platform consumption and avoid unnecessary costs using Atlassian's "Optimise Forge platform costs" guidance. Use when the user asks to optimize Forge app costs, reduce Forge invocations, lower GB-seconds, reduce storage or log usage, tune memory, replace polling, improve…

atlassian/forge-skills · 137 tokens

forge-app-review

Performs a lightweight pre-release readiness review of Atlassian Forge apps across manifest/module wiring, architecture, runtime compatibility, dependency posture, tests, deploy readiness, and obvious security, cost, or reliability smells. Use when the user asks "review my Forge app", "pre-deploy check", "is this app…

atlassian/forge-skills · 134 tokens

logic-review

Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…

hyhmrright/logic-lens · 161 tokens

logic-health

Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…

hyhmrright/logic-lens · 180 tokens