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.
git clone --depth 1 https://github.com/fakoli/fakoli-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/commands/fakoli/fakoli-plugins/gws-docs)<a href="https://agentmods.dev/commands/fakoli/fakoli-plugins/gws-docs"><img src="https://agentmods.dev/badge/commands/fakoli/fakoli-plugins/gws-docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/fakoli/fakoli-plugins/gws-docs"><img src="https://agentmods.dev/badge/commands/fakoli/fakoli-plugins/gws-docs.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00011 | $0.00306 |
| Opus 5.5 | $0.00004 | $0.00122 |
| Sonnet 5.5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
gws-docs 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 1mo 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.
What it actually says
/gws-docs
Manage Google Docs documents using the gws CLI.
Instructions
When this command is invoked, parse $ARGUMENTS to determine the operation.
Common Operations
Read a document:
gws docs documents get --params '{"documentId": "DOC_ID"}'
Append text to a document:
gws docs +write --document DOC_ID --text "Content to append"
Create a new document:
gws docs documents create --json '{"title": "Document Title"}'
URL Handling
Extract document ID from URLs:
https://docs.google.com/document/d/DOC_ID/edit→DOC_ID
Tips
- The
+writehelper appends text. For rich formatting, use the rawbatchUpdateAPI. - Use
--format jsonwhen you need to parse document structure programmatically. - To find a document, search Drive:
gws drive files list --params '{"q": "mimeType=\"application/vnd.google-apps.document\" and name contains \"QUERY\""}' --format table
Error Handling
- Exit code 2: Auth expired. Tell user to run
gws auth login.
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.
- 1mo ago First seen · 46 lines · 11 tokens per session scan A e9f706da9f74
gws-docs is a command published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 11 tokens to every session and 306 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
update
You are executing the /import:update command. Re-fetch documentation from original sources.
search
You are executing the /import:search command. Search within all cached documentation.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
spawn
You are executing the /hydra:spawn command. Start an agent in an existing worktree.
explain
Explain the subject in depth using the fixed four-part structure: What, Why, Example, Consequences. Treat the subject as the thing to be explained, not as a literal question.
optimize
Run the credo optimisation audit for the current repo: a freshness check, then a read-only scan (conflict hotspots, changelog fragments, test-stage convention, dogma settings, parallelism readiness, and - only if the user says Yes when asked before the scan - instruction consistency across the global and repo…