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-doctornpx skills add tokencanopy/e2a --skill e2a-doctorgit clone --depth 1 https://github.com/tokencanopy/e2aWrote 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.
[](https://agentmods.dev/skills/tokencanopy/e2a/e2a-doctor)<a href="https://agentmods.dev/skills/tokencanopy/e2a/e2a-doctor"><img src="https://agentmods.dev/badge/skills/tokencanopy/e2a/e2a-doctor.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00069 | $0.00827 |
| Opus 5 | $0.00034 | $0.00413 |
| Sonnet 5 | $0.00014 | $0.00165 |
| Haiku 4.5 | $0.00007 | $0.00083 |
Grade A, and why
e2a-doctor 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 4d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose and repair e2a
Start from the symptom
Identify the failing surface and the smallest safe target: an inbox address, domain,
webhook ID, message ID, time window, or exact error. Do not request message content
unless it is necessary to diagnose the symptom. Inspect the available e2a MCP tools;
use the e2a MCP whoami tool, never the shell command.
Keep diagnosis separate from repair. Begin MCP-first, read-only diagnosis with the existing authorization; do not create a second credential or alter configuration.
Read-only MCP diagnosis
Call whoami first, then load only the symptom's minimum reads from
the diagnostic matrix. Use get_agent or
list_agents only to establish inbox access; read get_protection and
list_pending_messages for holds; use list_suppressions and
list_agent_suppressions for recipient blocks; inspect get_domain and public,
read-only DNS for domain symptoms; inspect get_webhook and
list_webhook_deliveries for a webhook; and call get_message_lifecycle for one
message's observed transitions.
Do not convert a missing tool, account-only scope, 401/403, or unavailable permission
into a pass. Record it as an explicit skipped check, naming the unavailable read and
the scope or authorization needed. Do not call verify_domain, test_webhook,
redeliver_event, or any mutation while diagnosing.
Rank findings
Return a ranked list. Every finding must include {cause, evidence, impact, remediation} and state whether it is a definite configuration failure, authorization
failure, asynchronous pending state, or transient service failure. Rank definite,
high-impact causes above possibilities; keep evidence factual and targeted.
Treat accepted, scheduled, and pending_review as durable outcomes, not delivery
receipts. Do not retry them: a second send can duplicate mail. Report the lifecycle or
hold state, then wait for its next transition or an authorized human decision.
Offer guided repairs
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.
- 4d ago First seen · 75 lines · 69 tokens per session scan A 697e114b8da6
e2a-doctor is a skill published in the GitHub repository tokencanopy/e2a (184 stars, last pushed 4d ago), licensed Apache-2.0. It adds 69 tokens to every session and 827 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-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.
commune-agent-network
Requires COMMUNEAPIKEY environment variable. Get one at commune.email.
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…
skills
Email API for AI agents. Create inboxes, send/receive email, manage threads and webhooks.
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.