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/fakoli/fakoli-plugins/gws-schemanpx skills add fakoli/fakoli-plugins --skill gws-schemagit 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-schema)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/gws-schema"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/gws-schema.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.1 | $0.00026 | $0.00501 |
| Opus 5 | $0.00013 | $0.00251 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
gws-schema 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 2d 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 schema
Reference: See the
gws-sharedskill for auth, global flags, and security rules.
Introspect any Google Workspace API schema at runtime. Use this before executing unfamiliar API calls to understand the exact parameters, request body structure, and response types.
Why Use Schema Introspection
- Avoid guessing — see the exact JSON payload structure before writing
--json - Discover parameters — find required vs optional query/path parameters
- Explore types — inspect nested object schemas and enum values
- Resolve references — follow
$refpointers to see full type definitions
Syntax
# Introspect a method's parameters and request/response schemas
gws schema <service>.<resource>.<method>
# Introspect a type definition
gws schema <service>.<TypeName>
# Resolve $ref pointers to inline the full schema
gws schema <service>.<resource>.<method> --resolve-refs
Examples
Discover method parameters
# What parameters does drive files list accept?
gws schema drive.files.list
# What does the request body for calendar events insert look like?
gws schema calendar.events.insert
# What fields are in a Gmail message?
gws schema gmail.Message
Resolve nested references
# Inline all $ref pointers for the full picture
gws schema sheets.spreadsheets.create --resolve-refs
Explore before executing
# Step 1: Check the schema
gws schema drive.permissions.create
# Step 2: Now execute with confidence
gws drive permissions create \
--params '{"fileId": "FILE_ID"}' \
--json '{"role": "reader", "type": "user", "emailAddress": "[email protected]"}'
Tips
- Always run
gws schemabefore using an unfamiliar API method - Use
--resolve-refswhen the schema output contains$refpointers you want to see inline - Combine with
--helpfor flag-level docs:gws drive files list --help - The schema is fetched from Google's Discovery Service — it's always up to date
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.
- 2d ago First seen · 72 lines · 26 tokens per session scan A 2e479c0485c1
gws-schema is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 26 tokens to every session and 501 once invoked, about $0.0001 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
better-auth-knowledge-patch
Use this skill when implementing, upgrading, debugging, or reviewing Better Auth applications. Start with the quick references below, then load the topic file that matches the task.
caddy-knowledge-patch
Use this patch when writing or reviewing Caddyfile or JSON configuration, upgrading Caddy, building custom binaries, or operating Caddy's HTTP, proxy, certificate, and telemetry features.
clickhouse-knowledge-patch
Use this skill when writing, reviewing, upgrading, or operating ClickHouse SQL and server configurations. Start with the compatibility-sensitive items below, then load the topic reference that matches the task.
arch-knowledge-patch
Restart the daemon immediately after upgrading openssh to 9.8p1 because the old daemon cannot accept new connections.
axum-knowledge-patch
Axum 0.8 uses return-position impl Trait in FromRequestParts and FromRequest. Implement their methods with native async fn; do not retain the old #[asynctrait] annotation.
cloudflare-d1-knowledge-patch
Use this skill when designing, implementing, migrating, operating, or debugging Cloudflare D1 databases. Check the project’s Wrangler configuration, binding usage, database generation, account plan, and remote-versus-local command flags before applying guidance.