Borrowing it
Nothing to install: this file belongs to anton-abyzov/vskill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/anton-abyzov/vskill/main/.claude/skills/google-workspace/gws/SKILL.mdgit clone --depth 1 https://github.com/anton-abyzov/vskillWrote 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/anton-abyzov/vskill/gws)<a href="https://agentmods.dev/skills/anton-abyzov/vskill/gws"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/gws.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 324 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Agent Snooping · line 236 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00231 | $0.03161 |
| Opus 5 | $0.00115 | $0.01580 |
| Sonnet 5 | $0.00046 | $0.00632 |
| Haiku 4.5 | $0.00023 | $0.00316 |
Grade B, and why
gws scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Add to your Claude settings (e.g., `~/.claude/settings.json` or project `.claude/settings.json`): How it starts
The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Workspace CLI (gws)
One CLI for all of Google Workspace — Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and every API published via Google Discovery Service. Built in Rust, distributed via npm, designed for humans and AI agents.
Upstream: googleworkspace/cli (Apache 2.0) Status: Pre-v1.0 — breaking changes possible. Pin versions in production scripts.
When to Use gws vs Native Claude MCP
| Need | Use |
|---|---|
| Read/send Gmail | Native claude_ai_Gmail (already configured) |
| Calendar events | Native claude_ai_Google_Calendar (already configured) |
| Google Drive files | gws (no native integration) |
| Google Sheets | gws (no native integration) |
| Google Docs | gws (no native integration) |
| Google Chat | gws (no native integration) |
| Admin / Directory | gws (no native integration) |
| Bulk automation across services | gws (unified CLI, scriptable) |
| Custom/new Google APIs | gws (dynamic discovery picks up new APIs automatically) |
Installation
# Via npm (recommended — includes pre-built native binary)
npm install -g @googleworkspace/cli
# Verify
gws --version
Alternative: download pre-built binaries from GitHub Releases.
Authentication Setup
Prerequisites
- A Google Cloud project (create via console.cloud.google.com or
gcloud) - Required Google APIs enabled in the project (Drive API, Gmail API, etc.)
- OAuth consent screen configured (add test users if in testing mode)
Interactive Setup (Recommended)
# Guided setup — walks through GCP project configuration
gws auth setup
# OAuth login — opens browser for consent
gws auth login
# Verify authentication
gws auth status
Service Account (Headless/CI)
export GOOGLE_WORKSPACE_CLI_CREDENTIALS_FILE=/path/to/service-account.json
Pre-obtained Token
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.
- 8d ago First seen · 362 lines · 231 tokens per session scan B 285c7612aa4a
gws is a skill published in the GitHub repository anton-abyzov/vskill (45 stars, last pushed today), licensed MIT. It adds 231 tokens to every session and 3,161 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
help-flow
Help about Rosetta: explains capabilities and usage.
external-lib-flow
Workflow for onboarding an external private library so AI can use it without source access.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
coding-flow
Light coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
coding-agents-prompting-flow
Workflow for authoring and adapting AI-agent prompts: skills, agents, workflows, rules, etc.