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/jtsternberg/claude-plugins/gmail-readnpx skills add jtsternberg/claude-plugins --skill gmail-readgit clone --depth 1 https://github.com/jtsternberg/claude-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/jtsternberg/claude-plugins/gmail-read)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/gmail-read"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/gmail-read.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 | $0.00034 | $0.01285 |
| Opus 5 | $0.00017 | $0.00642 |
| Sonnet 5 | $0.00007 | $0.00257 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
gmail-read 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 4d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gmail Read
Search Gmail with a query, or fetch a single message by id, and get structured results back — subject, from, date, snippet, and optionally the full plain-text body (HTML stripped).
This skill only reads. It never sends, modifies labels, marks as read, or
deletes. For composing, see the sibling gmail-draft-from-markdown skill.
Prerequisites
# Codex: this path resolves under Claude Code; substitute the directory containing this plugin.
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}"
bash "$PLUGIN_ROOT/scripts/auth-preflight.sh"
Task
Run the entrypoint script, passing all arguments through:
# Codex: this path resolves under Claude Code; substitute the directory containing this SKILL.md.
SKILL_DIR="${CLAUDE_SKILL_DIR}"
bash "$SKILL_DIR/scripts/read.sh" $ARGUMENTS
If no arguments were provided, ask the user what to search for (subject
keywords, sender, date range, etc.). Gmail search operators are supported
verbatim (e.g. from:[email protected] newer_than:7d).
Arguments
| Arg | Required | Notes |
|---|---|---|
"<query>" |
one of query or --id |
Any Gmail search string. Use quotes. |
--id <messageId> |
one of query or --id |
Fetch a single message directly. |
--limit N |
no | Max results in search mode (default 10). |
--body |
no | In search mode, also fetch each message's body. Slower — one extra API call per hit. |
--account LABEL|EMAIL |
no | Override active gws account (accepts an account label or its email). Errors if no account matches. |
--pretty |
no | Human-readable output instead of JSON. |
Behavior
Search mode
gws gmail users messages listwith the query andmaxResults=limit.- For each message id, fetch headers + snippet (and body if
--body). - Emit one JSON object per line (NDJSON) so downstream tools can stream.
Each JSON object has:
{
"id": "...",
"threadId": "...",
"subject": "...",
"from": "...",
"to": "...",
"date": "...",
"snippet": "...",
"body": "..." // only present with --body
}
What ships with it
1 file 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.
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.
- 4d ago First seen · 133 lines · 34 tokens per session scan A e8b3490805da
gmail-read is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,285 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…