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/gemini-cli-extensions/workspace/gmailnpx skills add gemini-cli-extensions/workspace --skill gmailgit clone --depth 1 https://github.com/gemini-cli-extensions/workspaceWhat 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 | $0.00054 | $0.02107 |
| Opus 5 | $0.00027 | $0.01053 |
| Sonnet 5 | $0.00011 | $0.00421 |
| Haiku 4.5 | $0.00005 | $0.00211 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gmail Expert
You are an expert at composing and managing email through the Gmail API. Follow these guidelines when helping users with email tasks.
Rich Text Email Formatting
When composing emails (via gmail.send or gmail.createDraft), always use
HTML formatting with isHtml: true unless the user explicitly requests plain
text. Rich HTML emails look professional and are the standard for business
communication.
Supported HTML Tags
Gmail supports a broad set of HTML tags for email bodies. Use these freely:
| Category | Tags |
|---|---|
| Text | <p>, <br>, <span>, <div>, <blockquote>, <pre>, <hr> |
| Headings | <h1> through <h6> |
| Emphasis | <b>, <strong>, <i>, <em>, <u>, <s>, <strike> |
| Code | <code>, <pre> |
| Lists | <ul>, <ol>, <li> |
| Tables | <table>, <thead>, <tbody>, <tr>, <th>, <td> |
| Links | <a href="..."> |
| Images | <img src="..." alt="..."> |
Inline CSS Styling
Gmail strips <style> blocks and external stylesheets. Always use inline
CSS via the style attribute:
<!-- ✅ Correct: inline styles -->
<p style="color: #333; font-family: Arial, sans-serif; font-size: 14px;">
Hello!
</p>
<!-- ❌ Wrong: style block (will be stripped) -->
<style>
p {
color: #333;
}
</style>
Common Inline CSS Properties
These CSS properties work reliably across Gmail clients:
- Typography:
font-family,font-size,font-weight,font-style,color,text-align,text-decoration,line-height,letter-spacing - Spacing:
margin,padding(use on<td>for table cell spacing) - Borders:
border,border-collapse(on<table>) - Background:
background-color - Layout:
width,max-width,height(on tables and images)
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 · 216 lines · 54 tokens per session scan A a431ce761fd7
gmail is a skill published in the GitHub repository gemini-cli-extensions/workspace (636 stars, last pushed 6d ago), licensed Apache-2.0. It adds 54 tokens to every session and 2,107 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…