Borrowing it
Nothing to install: this file belongs to moose-lab/awesome-workplaces-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moose-lab/awesome-workplaces-skills/main/.agents/skills/gmail-waitlist/SKILL.mdgit clone --depth 1 https://github.com/moose-lab/awesome-workplaces-skillsWrote 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/moose-lab/awesome-workplaces-skills/gmail-waitlist)<a href="https://agentmods.dev/skills/moose-lab/awesome-workplaces-skills/gmail-waitlist"><img src="https://agentmods.dev/badge/skills/moose-lab/awesome-workplaces-skills/gmail-waitlist/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/moose-lab/awesome-workplaces-skills/gmail-waitlist"><img src="https://agentmods.dev/badge/skills/moose-lab/awesome-workplaces-skills/gmail-waitlist.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.00062 | $0.02820 |
| Opus 5 | $0.00031 | $0.01410 |
| Sonnet 5 | $0.00012 | $0.00564 |
| Haiku 4.5 | $0.00006 | $0.00282 |
Grade B, and why
gmail-waitlist scanned grade B with 2 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 12d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
Run `node server.js` and in another terminal: `curl -X POST http://localhost:3000/api/waitlist -H "Content-Type: application/json" -d '{"email":"[email protected]"}'` — expect `{"success":true}`. If `ECONNREFUSED`, the se Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Run `node server.js` and in another terminal: `curl -X POST http://localhost:3000/api/waitlist -H "Content-Type: application/json" -d '{"email":"[email protected]"}'` — expect `{"success":true}`. If `ECONNREFUSED`, the se How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gmail Waitlist
Overview
Build a complete email waitlist that sends a Gmail notification whenever someone signs up. The entire stack runs at zero cost using GCP OAuth, a Vercel serverless function, and the Gmail API. No database required — every signup arrives as an email in your inbox.
What you get:
api/waitlist.js— Vercel serverless function (receives email, sends you a Gmail notification)- Frontend form handler — async submit with loading/error/success states
- Gmail as the "database" — search, label, and export signups using Gmail's built-in tools
Total cost: $0/month for typical waitlist volumes (Vercel free tier + Gmail API free tier).
Prerequisites
Verify these are installed before proceeding:
- Google account with Gmail
- Node.js 18+ (
node --version) - gcloud CLI (
gcloud --version; install withbrew install google-cloud-sdkon macOS) - Vercel CLI (
vercel --version; install withnpm i -g vercel) - gws CLI (
npx @googleworkspace/cli --version; install withnpm i -g @googleworkspace/cli)
Phase 1: GCP Project Setup
Create a Google Cloud project, enable the Gmail API, and configure OAuth credentials.
Inputs: Google account, desired GCP project ID Outputs: GMAIL_CLIENT_ID, GMAIL_CLIENT_SECRET → save for Phase 2
Detailed walkthrough: See
references/gcp-setup.md
Steps
-
Create a GCP project and enable the Gmail API:
gcloud projects create YOUR_PROJECT_ID --name="Your Project Name" gcloud config set project YOUR_PROJECT_ID gcloud services enable gmail.googleapis.com -
Configure the OAuth consent screen at the Google Cloud Console:
- Select External user type
- Fill in the app name, user support email, and developer email
- Add the scope
https://www.googleapis.com/auth/gmail.send - Add your Gmail address as a test user
-
Create OAuth client credentials:
- Navigate to Credentials → Create Credentials → OAuth client ID
- CRITICAL: Select "Desktop app" as the application type
- Name it (e.g., "Waitlist CLI")
- Copy the Client ID and Client Secret
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 274 B
- examples/form-handler.js 2.4 KB runs code
- examples/server.js 2.3 KB runs code
- examples/vercel.json 90 B
- examples/waitlist.js 3.3 KB runs code
- references/gcp-setup.md 3.2 KB
- references/gmail-api.md 3.2 KB
- references/gws-auth.md 3.8 KB
- references/vercel-deploy.md 4.2 KB
- scripts/extract-refresh-token.js 2.2 KB runs code
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.
- 12d ago First seen · 261 lines · 62 tokens per session scan B edd37ecacec6
gmail-waitlist is a skill published in the GitHub repository moose-lab/awesome-workplaces-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 62 tokens to every session and 2,820 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…