Borrowing it
Nothing to install: this file belongs to djbelieny/nova. 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/djbelieny/nova/main/.claude/skills/gws-gmail/SKILL.mdgit clone --depth 1 https://github.com/djbelieny/novaWrote 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/djbelieny/nova/gws-gmail)<a href="https://agentmods.dev/skills/djbelieny/nova/gws-gmail"><img src="https://agentmods.dev/badge/skills/djbelieny/nova/gws-gmail.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.00016 | $0.00531 |
| Opus 5 | $0.00008 | $0.00266 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
gws-gmail 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 6d 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
92% identical to gws-gmail — 7 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.
What it actually says
gmail (v1)
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws gmail <resource> <method> [flags]
Helper Commands
| Command | Description |
|---|---|
+send |
Send an email |
+triage |
Show unread inbox summary (sender, subject, date) |
+reply |
Reply to a message (handles threading automatically) |
+reply-all |
Reply-all to a message (handles threading automatically) |
+forward |
Forward a message to new recipients |
+watch |
Watch for new emails and stream them as NDJSON |
API Resources
users
getProfile— Gets the current user's Gmail profile.stop— Stop receiving push notifications for the given user mailbox.watch— Set up or update a push notification watch on the given user mailbox.drafts— Operations on the 'drafts' resourcehistory— Operations on the 'history' resourcelabels— Operations on the 'labels' resourcemessages— Operations on the 'messages' resourcesettings— Operations on the 'settings' resourcethreads— Operations on the 'threads' resource
Discovering Commands
Before calling any API method, inspect it:
# Browse resources and methods
gws gmail --help
# Inspect a method's required params, types, and defaults
gws schema gmail.<resource>.<method>
Use gws schema output to build your --params and --json flags.
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.
- 6d ago First seen · 59 lines · 16 tokens per session scan A 3af575990450
gws-gmail is a skill published in the GitHub repository djbelieny/nova (5 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 531 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to gws-gmail, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
intent-recognition
Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embedsother (whether the other primitive appears embedded inside — an agent step inside a workflow, or a workflow invoked as an…
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.
config-evals
Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it…
one-off-operations
Handles one-off operations: the request is a concrete effect that happens once — export or copy data somewhere, a migration, a backfill, a cleanup — with no trigger, schedule, or reuse intent. The workflow is the vehicle, not the deliverable. Users rarely say "one-off"; infer it from the task's shape. Load before…
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.