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/fmind/dot/gwsnpx skills add fmind/dot --skill gwsgit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/gws)<a href="https://agentmods.dev/skills/fmind/dot/gws"><img src="https://agentmods.dev/badge/skills/fmind/dot/gws.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00044 | $0.00789 |
| Opus 5 | $0.00022 | $0.00394 |
| Sonnet 5 | $0.00009 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
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 yesterday.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Workspace CLI
Use gws for Google Workspace automation from the shell: authentication, API discovery, bounded reads, and verified writes across Drive, Docs, Sheets, Gmail, Calendar, and Chat. A connected Workspace app (host connector or MCP server) owns in-document editing when one is available.
Workflow
-
Resolve the profile:
gws auth statusconfirms the account and scopes without printing credentials; setGOOGLE_WORKSPACE_CLI_CONFIG_DIRto isolate profiles. -
Inspect the live schema: never guess resource names, parameters, or request bodies.
gws schema <service.resource.method> --resolve-refs -
Start with a bounded read: pass identifiers and filters through
--params; use--page-all --page-limit <n>only when every page is needed.gws drive files list --params '{"pageSize": 10}' --format json -
Prepare writes exactly: resolve stable file, spreadsheet, document, calendar, space, and message identifiers first; build the body as JSON and validate it against the schema before passing
--json. -
Write with authority: every write (create, edit, share, move, delete, send mail or Chat, change calendars, bulk update) needs explicit approval of the exact service, IDs or ranges, content, recipients, and sharing effects.
-
Apply the smallest call: no broad search followed by an unreviewed batch mutation; keep retries idempotent with stable request identifiers or a read-before-write guard where the API supports them.
-
Verify by reading back: fetch the changed resource and compare the requested fields; for messages and events, separate accepted API state from recipient-visible delivery.
Gotchas
gws auth exportprints decrypted credentials: never run it during ordinary work.gws auth statusis a live call: it may refresh OAuth credentials and query scope or API state; it is not an offline config inspection.- Exit code 2 is authentication: repair it explicitly; on validation or discovery errors, refresh the schema before changing the request.
- Apps Script:
gws scriptmanages projects;claspstays only for local push and pull of script sources.
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.
- yesterday First seen · 56 lines · 44 tokens per session scan A 072cc3423741
gws is a skill published in the GitHub repository fmind/dot (4 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 789 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
google-workspace-cli
Use gws across Workspace APIs with schema-first calls, profile isolation, bounded reads, and verified Drive, Docs, Sheets, Gmail, Calendar, or Chat writes.
handover
Write a self-contained follow-up prompt carrying this session's decisions, constraints, and verified findings into a fresh agent session. Use when handing unfinished work to a new context window.
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.