agent-email-patterns
Architecture patterns for AI agents that communicate over email -- why agents need dedicated inboxes rather than human email accounts, infrastructure/provider tradeoffs, one-inbox-per-agent, two-way conversation loops, human-in-the-loop drafts, WebSocket vs webhook event design, multi-agent topologies, OTP flows, and the threat model (prompt injection, webhook spoofing, credential exposure, data leakage). Use when designing how agents send, receive, and manage email conversations, evaluating whether an agent needs email, or choosing an email provider; do not use for AgentMail SDK method calls or basic send/receive implementation.
Install
With your agent
Install OMGSkills skill "agentmail-to/agentmail-plugins:skills/agent-email-patterns" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/agentmail-to/agentmail-plugins /tmp/agentmail-plugins && ln -s /tmp/agentmail-plugins/skills/agent-email-patterns ~/.claude/skills/agent-email-patternsFrom README
Agent Email Patterns Opinionated patterns for building AI agents that communicate over email. This skill covers architecture and security decisions, not SDK specifics. For AgentMail SDK , use the agentmail skill. Why agents need their own inboxes Giving an agent OAuth access to a human's Gmail account is the most common approach and the most dangerous: Over-permissioned: typical OAuth scopes (e.g.
More from this repo
agentmail
Used to build with the AgentMail TypeScript or Python SDK for inbox, message, thread, draft, attachment, domain,...
agentmail-cli
Operate AgentMail from a shell with the official CLI.
agentmail-mcp
Configure or troubleshoot the hosted AgentMail MCP server for Codex, Claude Code, Cursor, Claude.ai, ChatGPT, or...