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/vaayne/agent-kit/gwsnpx skills add vaayne/agent-kit --skill gwsgit clone --depth 1 https://github.com/vaayne/agent-kitWhat 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.00121 | $0.01305 |
| Opus 5 | $0.00060 | $0.00652 |
| Sonnet 5 | $0.00024 | $0.00261 |
| Haiku 4.5 | $0.00012 | $0.00130 |
Grade A, and why
gws 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gws — Google Workspace CLI
gws <service> <resource> [sub-resource] <method> [flags]
Helpers prefixed with + are high-level shortcuts — prefer them. Run gws <service> --help to discover all commands.
Key Flags
| Flag | Purpose |
|---|---|
--params '{"k":"v"}' |
URL/query parameters |
--json '{"k":"v"}' |
Request body |
--format table|yaml|csv |
Output format (default: json) |
--dry-run |
Validate without calling the API |
--page-all |
Auto-paginate (NDJSON) |
--upload <PATH> |
Upload file (multipart) |
Shell Quoting
- Wrap
--params/--jsonin single quotes:--params '{"pageSize":10}' - Sheet ranges contain
!which zsh expands. Use double quotes:--range "Sheet1!A1:D10"(never single quotes)
Services
Gmail
gws gmail +triage # unread summary
gws gmail +send --to [email protected] --subject "Hi" --body "Hello"
gws gmail +read --message-id MSG_ID
gws gmail +reply --message-id MSG_ID --body "Thanks"
gws gmail users messages list --params '{"userId":"me","q":"is:unread"}'
Drive
gws drive files list --params '{"pageSize":10}'
gws drive +upload --file ./report.pdf --name "Q4 Report" --parent FOLDER_ID
gws drive permissions create --params '{"fileId":"FILE_ID"}' \
--json '{"role":"reader","type":"user","emailAddress":"[email protected]"}'
Sheets
gws sheets +read --spreadsheet SHEET_ID --range "Sheet1!A1:D10"
gws sheets +append --spreadsheet SHEET_ID --range "Sheet1" --values '[["Alice",30]]'
Calendar
gws calendar +agenda
gws calendar +insert --summary "Sync" --start "2026-05-01T10:00:00" \
--end "2026-05-01T11:00:00" --attendees "[email protected],[email protected]"
gws calendar events list --params '{"calendarId":"primary","maxResults":10}'
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 · 143 lines · 121 tokens per session scan A 0af7aefcc500
gws is a skill published in the GitHub repository vaayne/agent-kit (53 stars, last pushed 6d ago), licensed MIT. It adds 121 tokens to every session and 1,305 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.