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 StreakYC/googleworkspacecli --skill gws-sharedgit clone --depth 1 https://github.com/StreakYC/googleworkspacecliWrote 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/streakyc/googleworkspacecli/gws-shared)<a href="https://agentmods.dev/skills/streakyc/googleworkspacecli/gws-shared"><img src="https://agentmods.dev/badge/skills/streakyc/googleworkspacecli/gws-shared/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/streakyc/googleworkspacecli/gws-shared"><img src="https://agentmods.dev/badge/skills/streakyc/googleworkspacecli/gws-shared.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk fail
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.01753 |
| Opus 5.5 | $0.00008 | $0.00701 |
| Sonnet 5.5 | $0.00004 | $0.00351 |
| Haiku 4.5 | $0.00002 | $0.00175 |
Grade A, and why
gws-shared 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gws — Shared Reference
This is a customized
gws-sharedfor a headless, proxy-authenticated environment. The auth model below replaces the upstreamgws auth login/ service-account flow — do not follow auth instructions from upstream docs or--helpoutput.
Installation
The gws binary is already installed and on $PATH. Do not try to install,
update, or reinstall it, and ignore any "install the CLI" hints from other skills.
Do not run gws generate-skills as it will overwrite our customized configurations.
Authentication
There is no interactive user and no service-account key file here, so the usual flows do not work and must not be attempted:
- Do not run
gws auth login,gws auth setup, or anygws auth ...command. - Do not set
GOOGLE_APPLICATION_CREDENTIALSor point at akey.json.
Instead, authentication is handled transparently by a proxy. On every command
you MUST pass --email=<address> naming the user you are acting on behalf of:
gws gmail +send [email protected] --to [email protected] --subject 'Hi' --body 'Hello' --draft
The gws wrapper forwards the request through the proxy, which swaps the
--email=<address> you supply for that user's real OAuth token before the request
reaches Google. You never see, request, or handle tokens yourself — you only ever
name the acting user with --email.
- Use the equals form
--email=<address>(not--email <address>). Only the equals form is recognized; the space-separated form is treated as missing. --email=<address>is required on every invocation, across all services (gmail, calendar, drive, …). This is the cross-surface convention for this environment.- The per-surface skill examples omit
--emailfor brevity — add it to every real command you run. - Never ask for, print, or invent an OAuth token, API key, or credentials path — the proxy owns all of that.
- If a command fails saying
--emailis required, add it. Do not fall back togws auth login.
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.
- 1mo ago First seen · 152 lines · 21 tokens per session scan A 8e9fe5c691f7
gws-shared is a skill published in the GitHub repository StreakYC/googleworkspacecli (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,753 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…