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-quick-refgit 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-quick-ref)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/gws-quick-ref"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/gws-quick-ref/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-quick-ref"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/gws-quick-ref.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.00029 | $0.01068 |
| Opus 5.5 | $0.00012 | $0.00427 |
| Sonnet 5.5 | $0.00006 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
gws-quick-ref 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gws Quick Reference
Reference: See the
gws-sharedskill for auth, global flags, and security rules.
Quick reference card for the gws CLI syntax and patterns.
Core Syntax
gws <service> <resource> [sub-resource] <method> [flags]
Getting Help
gws --help # All services
gws <service> --help # Service resources
gws <service> <resource> --help # Resource methods
gws <service> <resource> <method> --help # Method flags
Key Flags
| Flag | Purpose | Example |
|---|---|---|
--params '<JSON>' |
URL/query parameters | --params '{"userId": "me", "q": "is:unread"}' |
--json '<JSON>' |
Request body (POST/PUT/PATCH) | --json '{"name": "My File"}' |
--fields '<MASK>' |
Limit response fields | --fields "files(id,name)" |
--format <FMT> |
Output format | json, yaml, csv, table |
--page-all |
Auto-paginate (NDJSON output) | Streams all pages |
--page-limit N |
Limit pagination pages | --page-limit 3 |
--upload <PATH> |
Multipart file upload | --upload ./file.pdf |
--output <PATH> |
Download to file | --output ./download.pdf |
--dry-run |
Preview without executing | Shows what would happen |
--sanitize <TPL> |
Model Armor scan | Scans response for injection |
Common Patterns
1. Reading Data (GET/LIST)
# Always use --fields to minimize response size
gws drive files list \
--params '{"q": "name contains \"Report\"", "pageSize": 10}' \
--fields "files(id,name,mimeType)"
2. Writing Data (POST/PUT/PATCH)
# Always --dry-run first, then execute
gws calendar events insert \
--params '{"calendarId": "primary"}' \
--json '{"summary": "Meeting", "start": {...}, "end": {...}}' \
--dry-run
3. Pagination
# Auto-paginate all results (NDJSON — one JSON object per line)
gws admin users list --params '{"domain": "example.com"}' --page-all
# Limit to N pages
gws drive files list --page-limit 3
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 · 123 lines · 29 tokens per session scan A e4825ff7c007
gws-quick-ref is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 29 tokens to every session and 1,068 once invoked, about $0.0001 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 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.
productivity-retro
A guided review for looking back on a week, month, quarter, or year and choosing what to do next. It uses short formats such as KPT: Keep, Problem, and Try.
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.