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 agentmods add skills/googleworkspace/cli/gws-drive-uploadnpx skills add googleworkspace/cli --skill gws-drive-uploadgit clone --depth 1 https://github.com/googleworkspace/cliWhat 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 | $0.00015 | $0.00358 |
| Opus 5 | $0.00008 | $0.00179 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
gws-drive-upload 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 2d 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.
Copies of this mod
5 near-identical copies found in the catalogue:
- gws-drive-upload — 100% identical, 0 lines differ
- gws-drive-upload — 100% identical, 0 lines differ
- gws-drive-upload — 100% identical, 0 lines differ
- gws-drive-upload — 92% identical, 5 lines differ
- gws-drive-upload — 92% identical, 5 lines differ
What it actually says
drive +upload
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Upload a file with automatic metadata
Usage
gws drive +upload <file>
Flags
| Flag | Required | Default | Description |
|---|---|---|---|
<file> |
✓ | — | Path to file to upload |
--parent |
— | — | Parent folder ID |
--name |
— | — | Target filename (defaults to source filename) |
Examples
gws drive +upload ./report.pdf
gws drive +upload ./report.pdf --parent FOLDER_ID
gws drive +upload ./data.csv --name 'Sales Data.csv'
Tips
- MIME type is detected automatically.
- Filename is inferred from the local path unless --name is given.
[!CAUTION] This is a write command — confirm with the user before executing.
See Also
- gws-shared — Global flags and auth
- gws-drive — All manage files, folders, and shared drives commands
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.
- 2d ago First seen · 54 lines · 15 tokens per session scan A 7ffd4bdffab8
gws-drive-upload is a skill published in the GitHub repository googleworkspace/cli (30,691 stars, last pushed 7d ago), licensed Apache-2.0. It adds 15 tokens to every session and 358 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-30.
Other skills, from other repositories
managing-google-workspace
Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search). Supports MCP tools or CLI via uvx workspace-mcp --cli. Provides tool routing, workflows, and parameter guidance for 114 tools. Triggers for "check my email"…
configure
Step-by-step setup wizard for the GWS connector. Walks through creating a GCP project, getting OAuth credentials, and connecting accounts.
reauth
Re-authorize a connected GWS account to refresh tokens or pick up new OAuth scopes without changing account settings.
add-account
Connect a new Google account to the GWS connector with a custom label. Supports per-account OAuth credentials for different organizations.
remove-account
Disconnect a Google account from the GWS connector and delete its tokens.
set-default
Set the default GWS account used when no account is specified.