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/tokencanopy/e2a/e2a-setupnpx skills add tokencanopy/e2a --skill e2a-setupgit clone --depth 1 https://github.com/tokencanopy/e2aWhat 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.00061 | $0.00688 |
| Opus 5 | $0.00030 | $0.00344 |
| Sonnet 5 | $0.00012 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
e2a-setup 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up e2a
Boundaries
- This skill starts after the e2a plugin is installed; it cannot bootstrap the plugin that contains it.
- Do not change client configuration, create an inbox, or change DNS without the confirmation stated below. Use OAuth and never ask an interactive user for an API key.
- Do not change application code. Never send a test unless the user selects its recipient.
MCP bootstrap
- Inspect the current client's tool registry for e2a tools.
- If absent, first check whether the plugin is disabled or needs a reload before offering manual registration; do not create a duplicate registration.
- Only if registration is genuinely absent, explain the native flow from clients.md, confirm before a client-config write, then offer to register
https://api.e2a.dev/mcp. - Complete the client's OAuth flow, reload or restart if required, then call the e2a MCP
whoamitool — never Unix or shellwhoami. Treat auth failures as reauthorization; preserve configuration for operational failures.
Select or create the inbox
- For agent scope, use the
agent_emailfromwhoami. - For account scope, call
list_agents: honor an inbox named by the task, use the sole result, or ask the user to choose among several. - If none exists, defer inbox creation until the user chooses a shared or custom domain below.
Choose shared or custom domain
Ask whether the user wants the recommended shared domain or a custom domain.
- Shared: offer an address on
agents.e2a.dev, confirm the full address, then callcreate_agent. - Custom: confirm ownership and branded-address intent, then follow
custom-domains.md. After verification and one
user-driven post-verification
get_domaincapability read show the inbound and outbound state. If ready, ask for and show the complete branded address, obtain confirmation, then callcreate_agent. If not ready, report the precise resume step; do not poll.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 54 lines · 61 tokens per session scan A dc12c61889b0
e2a-setup is a skill published in the GitHub repository tokencanopy/e2a (184 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 688 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-30.
Other skills, from other repositories
commune-email
I give you a real email inbox and let you send, receive, search, and manage email threads programmatically via the Commune API. Every inbox I create is RFC 5322 compliant — replies thread correctly in any email client, including Gmail, Apple Mail, and Outlook.
commune-agent-network
Requires COMMUNEAPIKEY environment variable. Get one at commune.email.
commune-sms
I give you a real phone number and let you send and receive SMS messages programmatically via the Commune API. You can send texts to any number, read conversation threads, and list all your SMS conversations — all from within your OpenClaw agent.
skills
Email API for AI agents. Create inboxes, send/receive email, manage threads and webhooks.
shipmail
Operate Shipmail custom-domain business email, agent inboxes, calendars, booking pages, newsletters, webhooks, and related account resources through the Shipmail MCP server. Use when the user asks to read or triage a Shipmail inbox, draft or send email, reply to a message or thread, manage a mailbox or domain, check…
clawaimail
Email infrastructure for AI agents — create inboxes, send and receive real emails, search messages, manage threads. Alternative to AgentMail with MCP server, REST API, webhooks, and WebSocket streaming.