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/johnson7788/multiuserclaw/agentmailnpx skills add johnson7788/MultiUserClaw --skill agentmailgit clone --depth 1 https://github.com/johnson7788/MultiUserClawWhat 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.00041 | $0.01090 |
| Opus 5 | $0.00020 | $0.00545 |
| Sonnet 5 | $0.00008 | $0.00218 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
agentmail 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 3d 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.
This is a copy
92% identical to agentmail — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentMail — Agent-Owned Email Inboxes
Requirements
- AgentMail API key (required) — sign up at https://console.agentmail.to (free tier: 3 inboxes, 3,000 emails/month; paid plans from $20/mo)
- Node.js 18+ (for the MCP server)
When to Use
Use this skill when you need to:
- Give the agent its own dedicated email address
- Send emails autonomously on behalf of the agent
- Receive and read incoming emails
- Manage email threads and conversations
- Sign up for services or authenticate via email
- Communicate with other agents or humans via email
This is NOT for reading the user's personal email (use himalaya or Gmail for that). AgentMail gives the agent its own identity and inbox.
Setup
1. Get an API Key
- Go to https://console.agentmail.to
- Create an account and generate an API key (starts with
am_)
2. Configure MCP Server
Add to ~/.hermes/config.yaml (paste your actual key — MCP env vars are not expanded from .env):
mcp_servers:
agentmail:
command: "npx"
args: ["-y", "agentmail-mcp"]
env:
AGENTMAIL_API_KEY: "am_your_key_here"
3. Restart Hermes
hermes
All 11 AgentMail tools are now available automatically.
Available Tools (via MCP)
| Tool | Description |
|---|---|
list_inboxes |
List all agent inboxes |
get_inbox |
Get details of a specific inbox |
create_inbox |
Create a new inbox (gets a real email address) |
delete_inbox |
Delete an inbox |
list_threads |
List email threads in an inbox |
get_thread |
Get a specific email thread |
send_message |
Send a new email |
reply_to_message |
Reply to an existing email |
forward_message |
Forward an email |
update_message |
Update message labels/status |
get_attachment |
Download an email attachment |
Procedure
Create an inbox and send an email
- Create a dedicated inbox:
- Use
create_inboxwith a username (e.g.hermes-agent) - The agent gets address:
[email protected]
- Use
- Send an email:
- Use
send_messagewithinbox_id,to,subject,text
- Use
- Check for replies:
- Use
list_threadsto see incoming conversations - Use
get_threadto read a specific thread
- Use
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.
- 3d ago First seen · 127 lines · 41 tokens per session scan A 12e10595db82
agentmail is a skill published in the GitHub repository johnson7788/MultiUserClaw (317 stars, last pushed 21d ago), licensed MIT. It adds 41 tokens to every session and 1,090 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to agentmail, differing in 19 lines, and is treated as a copy.
Other skills, from other repositories
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
organize-threads
猫猫辅助整理未分类 thread，分析标题和元数据，建议合适的标签。 Use when: 用户说"帮我整理"、"分类 thread"、点击整理按钮。 Not for: 删除/编辑标签本身。 Output: 按 thread 的标签建议列表。.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ralph-hats
Create, inspect, validate, explain, and improve Ralph hat collections. Use this skill whenever the user asks to make or refine a .ralph/hats/.yml workflow, debug hat routing, explain event topology, or tune a multi-hat Ralph run.