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 skills add fakoli/fakoli-plugins --skill gws-eventsgit 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/skills/fakoli/fakoli-plugins/gws-events)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/gws-events"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/gws-events/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/skills/fakoli/fakoli-plugins/gws-events"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/gws-events.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.00010 | $0.00721 |
| Opus 5.5 | $0.00004 | $0.00288 |
| Sonnet 5.5 | $0.00002 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
gws-events 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.
This is a copy
97% identical to gws-events — 10 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
events (v1)
Reference: See the
gws-sharedskill for auth, global flags, and security rules.
gws events <resource> <method> [flags]
Helper Commands
| Command | Description |
|---|---|
+subscribe |
Subscribe to Workspace events and stream them as NDJSON |
+renew |
Renew/reactivate Workspace Events subscriptions |
API Resources
message
stream— SendStreamingMessage is a streaming call that will return a stream of task update events until the Task is in an interrupted or terminal state.
operations
get— Gets the latest state of a long-running operation. Clients can use this method to poll the operation result at intervals as recommended by the API service.
subscriptions
create— Creates a Google Workspace subscription. To learn how to use this method, see Create a Google Workspace subscription.delete— Deletes a Google Workspace subscription. To learn how to use this method, see Delete a Google Workspace subscription.get— Gets details about a Google Workspace subscription. To learn how to use this method, see Get details about a Google Workspace subscription.list— Lists Google Workspace subscriptions. To learn how to use this method, see List Google Workspace subscriptions.patch— Updates or renews a Google Workspace subscription. To learn how to use this method, see Update or renew a Google Workspace subscription.reactivate— Reactivates a suspended Google Workspace subscription. This method resets your subscription'sStatefield toACTIVE. Before you use this method, you must fix the error that suspended the subscription. This method will ignore or reject any subscription that isn't currently in a suspended state. To learn how to use this method, see Reactivate a Google Workspace subscription.
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 · 61 lines · 10 tokens per session scan A f5b7e7af3a87
gws-events is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 721 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to gws-events, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
fp-yoohoo
Terminal-recall mode. Reference for fp-yoohoo, the plugin that brings the terminal window to the foreground when Claude Code stops and waits on a human: a permission prompt, a question dialog, a plan to approve. Explains what it hooks, which desktops it can raise a window on, how the already-focused guard works, and…
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
collab-feedback-loop
A guide for giving and receiving workplace feedback about specific actions and their effects.
book-publishing
Multi-book content, voice, and production workflows for nonfiction authoring. Use when planning a book, maintaining consistent voice across chapters, structuring a manuscript, or running an end-to-end publishing pipeline.
nextjs-expert
Comprehensive Next.js expertise across App Router, server/client boundaries, data and caching patterns, and production operations. Use when building, debugging, or optimizing a Next.js app, deciding server vs client components, or resolving App Router gotchas.
mcp-architecture
Design and implement Model Context Protocol servers with resources, tools, prompts, and security best practices. Use when architecting an MCP server, modeling its resources/tools/prompts, or integrating a service as an MCP endpoint.