agentmail

Name: agentmail
Author: NousResearch

AI Verified v1.0.0

Repo stars 164,280
Author updated Live
Author repo hermes-agent

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: AI
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 92 / 100 · audit passed
Author / version / license: @NousResearch · v1.0.0 · no license declared
Token usage: Lean
Setup complexity: Guided setup
External API key: Required · Vendor-specific
Operating systems: macOS · Linux · Windows
Runtime requirements: Node.js · Python
Permissions: Read-only
Write / modify
Env read
Network behavior: External requests
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview agentmail.preview

---
name: agentmail
description: Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email auto…
category: ai
runtime: Node.js / Python
---

# agentmail output preview

## PART A: Task fit
- Use case: Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-owned email addresses (e.g. hermes-agent@agentmail.to)..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Requirements / When to Use / Setup” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-owned email addresses (e.g. hermes-agent@agentmail.to).”.
- **02** When the source has headings, the agent prioritizes “Requirements / When to Use / Setup” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, read environment variables; may access external network resources; requires Vendor-specific API keys.

## Running Rules
- read files, write/modify files, read environment variables; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: agentmail
description: Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email auto…
category: ai
source: NousResearch/hermes-agent
---

# agentmail

## When to use
- Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-o…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Requirements / When to Use / Setup” and keep inference separate from source facts.
- read files, write/modify files, read environment variables; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "agentmail" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Requirements / When to Use / Setup
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> Node.js / Python | read files, write/modify files, read environment variables | may access external network resources
  guardrails -> requires Vendor-specific API keys + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-owned email…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Requirements”, “When to Use”, “Setup”, “1. Get an API Key”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name agentmail directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Requirements / When to Use / Setup” before expanding.

Boundaries And Review

Dependencies: Prepare Vendor-specific API keys before running a full task.
Permissions: Declared permissions include read / write / env-read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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_inbox with a username (e.g. hermes-agent)
- The agent gets address: hermes-agent@agentmail.to
Send an email:
- Use send_message with inbox_id, to, subject, text
Check for replies:
- Use list_threads to see incoming conversations
- Use get_thread to read a specific thread

Check incoming email

Use list_inboxes to find your inbox ID
Use list_threads with the inbox ID to see conversations
Use get_thread to read a thread and its messages

Reply to an email

Get the thread with get_thread
Use reply_to_message with the message ID and your reply text

Example Workflows

Sign up for a service:

1. create_inbox (username: "signup-bot")
2. Use the inbox address to register on the service
3. list_threads to check for verification email
4. get_thread to read the verification code

Agent-to-human outreach:

1. create_inbox (username: "hermes-outreach")
2. send_message (to: user@example.com, subject: "Hello", text: "...")
3. list_threads to check for replies

Pitfalls

Free tier limited to 3 inboxes and 3,000 emails/month
Emails come from @agentmail.to domain on free tier (custom domains on paid plans)
Node.js (18+) is required for the MCP server (npx -y agentmail-mcp)
The mcp Python package must be installed: pip install mcp
Real-time inbound email (webhooks) requires a public server — use list_threads polling via cronjob instead for personal use

Verification

After setup, test with:

hermes --toolsets mcp -q "Create an AgentMail inbox called test-agent and tell me its email address"

You should see the new inbox address returned.

References

AgentMail docs: https://docs.agentmail.to/
AgentMail console: https://console.agentmail.to
AgentMail MCP repo: https://github.com/agentmail-to/agentmail-mcp
Pricing: https://www.agentmail.to/pricing

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add NousResearch/hermes-agent/optional-skills/email/agentmail -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

92 / 100

Verified

未声明 license/许可。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
NousResearch/hermes-agent
Version: 1.0.0
中文

Category & tags

Category AI