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/cblecker/claude-plugins/gws-drivenpx skills add cblecker/claude-plugins --skill gws-drivegit clone --depth 1 https://github.com/cblecker/claude-pluginsWrote 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/cblecker/claude-plugins/gws-drive)<a href="https://agentmods.dev/skills/cblecker/claude-plugins/gws-drive"><img src="https://agentmods.dev/badge/skills/cblecker/claude-plugins/gws-drive.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.00016 | $0.03069 |
| Opus 5 | $0.00008 | $0.01535 |
| Sonnet 5 | $0.00003 | $0.00614 |
| Haiku 4.5 | $0.00002 | $0.00307 |
Grade A, and why
gws-drive 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 today.
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.
This is a copy
100% identical to gws-drive — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
drive (v3)
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws drive <resource> <method> [flags]
Helper Commands
| Command | Description |
|---|---|
+upload |
Upload a file with automatic metadata |
API Resources
about
get— Gets information about the user, the user's Drive, and system capabilities. For more information, see Return user info. Required: Thefieldsparameter must be set. To return the exact fields you need, see Return specific fields.
accessproposals
get— Retrieves an access proposal by ID. For more information, see Manage pending access proposals.list— List the access proposals on a file. For more information, see Manage pending access proposals. Note: Only approvers are able to list access proposals on a file. If the user isn't an approver, a 403 error is returned.resolve— Approves or denies an access proposal. For more information, see Manage pending access proposals.
approvals
get— Gets an Approval by ID.list— Lists the Approvals on a file.
apps
get— Gets a specific app. For more information, see Return user info.list— Lists a user's installed apps. For more information, see Return user info.
changes
getStartPageToken— Gets the starting pageToken for listing future changes. For more information, see Retrieve changes.list— Lists the changes for a user or shared drive. For more information, see Retrieve changes.watch— Subscribes to changes for a user. For more information, see Notifications for resource changes.
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.
- today Changed · +1 lines d37fad56bb95
- 4d ago First seen · 138 lines · 16 tokens per session scan A 43f4bf424ca8
gws-drive is a skill published in the GitHub repository cblecker/claude-plugins (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 3,069 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gws-drive, differing in 0 lines, and is treated as a copy.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…