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 recipe-schema-exploregit 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/recipe-schema-explore)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-schema-explore"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-schema-explore.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.00025 | $0.00435 |
| Opus 5 | $0.00013 | $0.00217 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
recipe-schema-explore 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 3d 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
Explore an API Before Using It
Discover and introspect any Google Workspace API using gws schema before executing commands.
When to Use
Use this workflow when the user wants to explore an unfamiliar API, check method parameters, or understand the request/response structure before making calls.
Steps
-
List available methods for a service:
gws <service> --helpExample:
gws drive --help gws sheets --help -
Drill into a resource:
gws drive files --help gws sheets spreadsheets --help -
Inspect method parameters:
gws schema drive.files.list gws schema calendar.events.insert -
Resolve nested type references:
gws schema sheets.spreadsheets.create --resolve-refs -
Inspect a specific type:
gws schema gmail.Message gws schema drive.File -
Test with a dry run:
gws drive files list \ --params '{"pageSize": 3}' \ --fields "files(id,name)" \ --dry-run -
Execute with confidence:
gws drive files list \ --params '{"pageSize": 3}' \ --fields "files(id,name)"
Tips
- Always start with
gws schemawhen using an API for the first time - Use
--resolve-refsto see the full schema without chasing$refpointers - The schema data comes from Google's live Discovery Service — always current
- Combine
--help(for CLI flags) withgws schema(for API structure)
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.
- 3d ago First seen · 70 lines · 25 tokens per session scan A 349375a4d948
recipe-schema-explore is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 435 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
explain
Explain something in depth on request. Use when the user writes "???" - alone, or placed directly after a reference, statement, or term - which means "explain that in more detail, with a concrete example AND consequences". Also invoked by the /credo:explain command. Treat the pointed-at subject as the thing to…
a-unslop-code
Finds what makes source code read as AI-written and points you at the parts that actually ship bugs. Sorts every tell into three buckets and fixes them in that order: bugs (swallowed errors, a made-up API, a left-in "rest of the code" stub), substance (tutorial-shaped boilerplate, over-engineering, code that ignores…
zasilkovna
Integrate and manage Zásilkovna (Packeta) shipping for Czech and Slovak logistics. Create shipments, generate labels, track packages, manage pickup points, and configure webhooks using the Zásilkovna API. Covers both the REST API and SOAP API. Includes ready-to-run CLI scripts for all API operations. Context: User…
media-higgsfield-explainer
A Higgsfield workflow for making non-photorealistic narrated explainer videos. It pairs each narration line with a 10-second animated clip and joins the clips into one finished video.
career-junior-onboarding
A self-onboarding coach for new and junior employees during their first 90 days at a company. Onboarding means learning how the organization, people, tools, and work processes operate.
push-notifications
Generate push notification infrastructure with APNs registration, handling, and rich notifications. Use when adding push notifications, configuring APNs, notification categories/actions, or rich notifications with images and custom UI.