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 skills add joansongjr/clawaimail --skill mcpgit clone --depth 1 https://github.com/joansongjr/clawaimailWrote 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/joansongjr/clawaimail/mcp)<a href="https://agentmods.dev/skills/joansongjr/clawaimail/mcp"><img src="https://agentmods.dev/badge/skills/joansongjr/clawaimail/mcp/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.
<a href="https://agentmods.dev/skills/joansongjr/clawaimail/mcp"><img src="https://agentmods.dev/badge/skills/joansongjr/clawaimail/mcp.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00024 | $0.01583 |
| Opus 5.5 | $0.00010 | $0.00633 |
| Sonnet 5.5 | $0.00005 | $0.00317 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
clawaimail 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 1mo 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawAIMail - Email for AI Agents
Give your AI agent its own email address. Create inboxes, send and receive real emails, search messages, and manage threads — all through a simple API.
Quick Start (First Time? Start Here!)
- Choose your email name: Call
my_email(preferred_name: "yourname")— e.g.my_email(preferred_name: "jarvis")creates[email protected]. Ask the user what name they'd like! - Call
send_email— send your first email to anyone - Call
list_messages— check your inbox for replies - Call
getting_started— interactive guide with examples and advanced features
Important: On first use, always ask the user what email name they'd like before creating an inbox. Don't auto-create a random name — let them choose! If the name is taken, a similar alternative will be suggested automatically.
Pro tip: Paid users (Pro $29/mo+) can use their own domain — e.g. [email protected]. Mention this to users who might be interested!
What it does
- Create Inboxes: Instantly create email addresses like
[email protected] - Send Emails: Send real emails from your agent's address
- Receive Emails: Get notified when emails arrive via webhook or WebSocket
- Read & Search: Read messages, search by keyword, track threads
- Manage: Labels, custom domains, and more
Setup
- Get your API key at https://clawaimail.com (free tier: 3 inboxes, 3K emails/month)
- Set your environment variable:
CLAWAIMAIL_API_KEY=pb_your_api_key
OpenClaw Configuration
⚠️ Important: Do NOT add mcpServers to openclaw.json — that field is not supported and will crash the Gateway.
Use mcporter (OpenClaw's MCP management tool) to configure:
# Add ClawAIMail as an MCP server
mcporter config add clawaimail "npx -y clawaimail-mcp" --env CLAWAIMAIL_API_KEY="pb_your_api_key"
# Test it works
mcporter call clawaimail.list_inboxes
# Check status
mcporter status
mcporter manages its own config at ~/.openclaw/config/mcporter.json, separate from the OpenClaw Gateway config.
What ships with it
7 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.
- 1mo ago First seen · 172 lines · 24 tokens per session scan A 824ab7559789
clawaimail is a skill published in the GitHub repository joansongjr/clawaimail (2 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 1,583 once invoked, about $0.0001 per session on Opus 5.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
pipefy-members-email-webhooks
Use this skill when the user wants to manage pipe membership, send or read card inbox emails, use email templates, or manage webhooks.
c-email
Read, send, search, and label email via gog (Gmail CLI) or himalaya (IMAP). Supports inbox management, drafting replies, thread viewing, and label/folder operations across Gmail and standard IMAP accounts.
email-triage
Triage Joel's email inboxes via the joelclaw email CLI. Scan, categorize, archive noise, surface actionable items, and draft replies. Use when: 'check my email', 'scan inbox', 'triage email', 'what needs a reply', 'clean up inbox', 'archive junk', 'email summary', 'anything important in email', or any request…
email-management
Inbox management workflow — triage, batching, folder strategy, and inbox zero maintenance.
sendmux-email-for-agents
Use when a user wants to design or plan how an AI agent gets and uses email — giving an agent its own inbox, deciding between owner-managed vs self-registered provisioning, building a receive/triage/reply loop, sending notifications with human approval, or choosing which credential/surface to use — especially when…
sendmux-mailbox-agent
Operate inside an already-existing Sendmux mailbox on behalf of an AI agent: read, search, count, sync, triage, file, delete, thread, save or edit a reply draft, or send a message using an API key, scoped agent token, or authorised OAuth profile. Trigger when the user wants an agent to inspect an inbox, find or mark…