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/thrownlemon/claude-code-plugins/emailnpx skills add ThrownLemon/claude-code-plugins --skill emailgit clone --depth 1 https://github.com/ThrownLemon/claude-code-pluginsWhat 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.00026 | $0.00603 |
| Opus 5 | $0.00013 | $0.00302 |
| Sonnet 5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
email 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 yesterday.
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
Gmail Email Management
When the user wants to manage their email from the terminal, delegate to the gmail-assistant subagent.
When to Use
Use this skill when the user:
- Asks to check their email or inbox
- Wants to search for specific emails
- Needs to read an email thread
- Wants to send or compose an email
- Mentions Gmail or email management
- Asks about unread messages
What the Subagent Handles
The gmail-assistant subagent uses gmcli to:
-
Search Emails
- Use Gmail query syntax
- Return formatted results
- Offer to read specific threads
-
Read Threads
- Display full conversation
- Show attachments
- Offer follow-up actions
-
Send Emails
- Compose with to/cc/bcc
- Support attachments
- Confirm before sending
-
Manage Drafts
- Create, edit, delete drafts
- Send saved drafts
-
Handle Labels
- List available labels
- Add/remove labels from threads
- Archive messages
Default Behaviors
- "Check my email" - Search for unread emails:
is:unread newer_than:1d - "Any new emails?" - Same as above
- "Check inbox" - Show recent inbox:
in:inbox newer_than:1d - "Email from X" - Search:
from:X
Setup Required
If gmcli is not installed or configured, the subagent will guide the user through setup:
- Install via npm
- Configure Google OAuth credentials
- Add Gmail account
Example Triggers
- "Check if I have any new emails"
- "Search for emails from John about the project"
- "Send an email to [email protected]"
- "Read that email thread"
- "Check my inbox for unread messages"
- "Any emails from my boss today?"
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.
- yesterday First seen · 96 lines · 26 tokens per session scan A cccdb3928164
email is a skill published in the GitHub repository ThrownLemon/claude-code-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 603 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-08-31.
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…