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/drn/dots/emailnpx skills add drn/dots --skill emailgit clone --depth 1 https://github.com/drn/dotsWhat 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.00023 | $0.00730 |
| Opus 5 | $0.00012 | $0.00365 |
| Sonnet 5 | $0.00005 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
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 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email (Read-Only)
Search and read Gmail messages using the gmail CLI.
Instructions
You are helping read Gmail data. Auth uses OAuth tokens stored at ~/.dots/sys/gmail/tokens/. Additional env vars (if any) are loaded from ~/.dots/sys/env.
Operations
# Search emails
gmail search "from:emily subject:kickoff" # Search by sender and subject
gmail search "is:unread" --limit 10 # Recent unread
gmail search "after:2025/01/01 from:sarah" # Date-filtered search
# Read a specific email
gmail read MESSAGE_ID # Read full email by ID
# List labels with message counts
gmail labels
# List configured accounts
gmail accounts
# Use a specific account
gmail search "budget" --account personal
gmail labels --account work
# Re-authenticate an account (opens browser for OAuth)
gmail auth personal
# JSON output
gmail search "quarterly review" --json
gmail accounts --json
Accounts
Run gmail accounts to see configured accounts with names and emails. The default account is marked with *.
Common Tasks
Find recent emails from someone
gmail search "from:emily" --limit 10
Read an email thread
# First search to find message IDs
gmail search "subject:technical kickoff" --limit 5
# Then read the specific message
gmail read MESSAGE_ID
Check unread count
gmail labels
Account Resolution
The CLI resolves accounts in this order:
--account NAMEflag — uses~/.dots/sys/gmail/tokens/NAME.json- Default account from
~/.dots/sys/gmail/accounts.json - First token file found in
~/.dots/sys/gmail/tokens/
Search Syntax
Gmail search supports standard Gmail query operators:
from:sender— messages from a specific senderto:recipient— messages to a specific recipientsubject:words— subject line searchafter:YYYY/MM/DD/before:YYYY/MM/DD— date rangeis:unread/is:starred— message statehas:attachment— messages with attachmentslabel:NAME— messages with a specific labelin:inbox/in:sent— location filters
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 · 105 lines · 23 tokens per session scan A f8d67fa0375d
email is a skill published in the GitHub repository drn/dots (23 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 730 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-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…