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/ericboehs/claude-plugins/check-emailnpx skills add ericboehs/claude-plugins --skill check-emailgit clone --depth 1 https://github.com/ericboehs/claude-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.00035 | $0.00813 |
| Opus 5 | $0.00017 | $0.00407 |
| Sonnet 5 | $0.00007 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
check-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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Email (himalaya)
Manage email from the command line using himalaya with local Maildir sync via mbsync.
Accounts
| Name | Provider | Usage |
|---|---|---|
personal |
Fastmail (default) | Personal email |
oddball |
Google Workspace | Work/VA email |
The default account is personal. Use -a oddball for work email.
Prerequisites
himalaya must be installed and configured. If any command fails with "command not found", suggest running /setup-email.
Email is synced to local Maildir (~/Mail/) via mbsync + IMAP IDLE (near-instant). Himalaya reads from local Maildir — no network needed for reading.
Commands
List inbox (unread envelopes)
# Personal inbox (default)
himalaya envelope list
# Work inbox
himalaya envelope list -a oddball
# List a specific folder
himalaya envelope list -f Sent
himalaya envelope list -f "[Gmail]/Sent Mail" -a oddball
Read a message
# Read by ID (from envelope list output)
himalaya message read <id>
# Read from work account
himalaya message read <id> -a oddball
Mark as read
himalaya flag add <id> seen
himalaya flag add <id> seen -a oddball
Archive messages
Use the mail-archive script (not raw himalaya move) — it handles UID stripping for mbsync compatibility:
# Archive from personal (moves to Archive folder)
mail-archive <id> [id...]
# Archive from work/Gmail (moves to [Gmail]/All Mail)
mail-archive -a oddball <id> [id...]
Sync email manually
# Sync all accounts
mbsync -a
# Sync a single account
mbsync personal
mbsync work
# Full pipeline (sync + text extraction + search index update)
mail-sync -a
Search email
Use qmd for full-text search across all indexed email:
# Fast keyword search (BM25)
qmd search "quarterly report" -c email
# Semantic search with reranking (slower, more relevant results)
qmd query "emails about the server migration timeline" -c email -n 5
# Search across everything — email, wiki, notes
qmd query "meeting with Alex about deployment"
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 · 119 lines · 35 tokens per session scan A 83291320d80d
check-email is a skill published in the GitHub repository ericboehs/claude-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 35 tokens to every session and 813 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.