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-scriptnpx skills add googleworkspace/cli --skill gws-scriptgit 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.00010 | $0.00502 |
| Opus 5 | $0.00005 | $0.00251 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
gws-script 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
2 near-identical copies found in the catalogue:
- gws-script — 100% identical, 0 lines differ
- gws-script — 100% identical, 0 lines differ
What it actually says
script (v1)
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws script <resource> <method> [flags]
Helper Commands
| Command | Description |
|---|---|
+push |
Upload local files to an Apps Script project |
API Resources
processes
list— List information about processes made by or on behalf of a user, such as process type and current status.listScriptProcesses— List information about a script's executed processes, such as process type and current status.
projects
create— Creates a new, empty script project with no script files and a base manifest file.get— Gets a script project's metadata.getContent— Gets the content of the script project, including the code source and metadata for each script file.getMetrics— Get metrics data for scripts, such as number of executions and active users.updateContent— Updates the content of the specified script project. This content is stored as the HEAD version, and is used when the script is executed as a trigger, in the script editor, in add-on preview mode, or as a web app or Apps Script API in development mode. This clears all the existing files in the project.deployments— Operations on the 'deployments' resourceversions— Operations on the 'versions' resource
scripts
run—
Discovering Commands
Before calling any API method, inspect it:
# Browse resources and methods
gws script --help
# Inspect a method's required params, types, and defaults
gws schema script.<resource>.<method>
Use gws schema output to build your --params and --json flags.
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 · 63 lines · 10 tokens per session scan A 80bef63fdbdc
gws-script is a skill published in the GitHub repository googleworkspace/cli (30,651 stars, last pushed 6d ago), licensed Apache-2.0. It adds 10 tokens to every session and 502 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.
add-account
Connect a new Google account to the GWS connector with a custom label. Supports per-account OAuth credentials for different organizations.
reauth
Re-authorize a connected GWS account to refresh tokens or pick up new OAuth scopes without changing account settings.
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.