What is email-manager?

Instructions for managing email across configured accounts through email tools, including searching, reading, replying, archiving, and batch actions.

Use it when checking inboxes, finding unread mail, replying, archiving, moving, flagging, or deleting messages.

It defines safe handling for account selection, sending messages, permanent deletion, authentication problems, and large groups of messages.

email-manager — Skill for Claude Code and Codex by sasha-id

Install

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.

Any agent

npx skills add sasha-id/email-mcp --skill email-manager

Clone the repo

git clone --depth 1 https://github.com/sasha-id/email-mcp

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sasha-id/email-mcp/email-manager/github.svg)](https://agentmods.dev/skills/sasha-id/email-mcp/email-manager)

Your own site

<a href="https://agentmods.dev/skills/sasha-id/email-mcp/email-manager"><img src="https://agentmods.dev/badge/skills/sasha-id/email-mcp/email-manager/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sasha-id/email-mcp/email-manager"><img src="https://agentmods.dev/badge/skills/sasha-id/email-mcp/email-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 717 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.1	$0.00052	$0.00717
Opus 5	$0.00026	$0.00358
Sonnet 5	$0.00010	$0.00143
Haiku 4.5	$0.00005	$0.00072

Measured 9d ago against content hash 4807c939b07e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

email-manager 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 9d 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.

skills/email-manager/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Email Manager

Orchestrates the email_* MCP tools (email-mcp server). All tools are account-scoped; message identity is {account, mailbox, uid}.

Ground rules

Start with email_list_accounts when account names are not already known in this conversation. Never guess account names.
Confirm before sending. Show the user recipient(s), subject, and body before calling email_send. Same for email_delete with permanent: true — that one is irreversible. Trash-deletes, flag changes, and moves do not need confirmation.
Batch mutations. Collect uids from email_search, then issue ONE email_mark/email_move/email_delete call with uids: [...] — never one call per message.
M365 auth expiry. If a tool fails with "run email_authenticate", call email_authenticate for that account, give the user the URL + code, and retry the original call after they confirm login (check with another email_authenticate call).
Keep output small. Default search limit is 20; raise it only when the user asks. Use email_read on selected uids, not on whole result lists.

Workflows

Cross-account triage ("anything new?", "check my email")

email_list_accounts
email_search per account in parallel with { seen: false }
Summarize per account: count + one line per notable message (sender, subject). Flag anything urgent-looking.

Read / summarize a thread

email_search with subject/from to find the messages
email_read each relevant uid (newest first, stop when context suffices)
Synthesize; offer to reply.

Reply in-thread

Locate the message (email_search, note account, mailbox, uid)
Draft the reply body; show the user
On approval: email_send with replyTo: { mailbox, uid } — recipients and "Re:" subject default from the original; threading headers are set automatically.

Bulk archive/cleanup ("archive all newsletters from X")

email_search with from/subject filters (raise limit if needed)
Show the user the matching list briefly
email_list_folders to find the archive/target folder
One email_move with all uids.

Read the full file on GitHub · 65 lines

Changes

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.

9d ago First seen · 65 lines · 52 tokens per session scan A 4807c939b07e

Subscribe to this mod's changes

email-manager is a skill published in the GitHub repository sasha-id/email-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 717 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-31.

Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

email-manager