agentmaillisted

Spin up disposable email inboxes via myagentinbox.com for tests, signup flows, OTP/magic-link captures, and any task that needs to receive mail from a service without using a real mailbox. Provides a REST-first bash workflow (no MCP required), 24h-lifetime inboxes, polling helpers with timeout, and verification-code/magic-link extractors. Use when the user mentions "throwaway email", "disposable inbox", "test signup", "OTP capture", "magic link", "verify email flow", "/expect-test signup", or any flow where a service emails a code and the agent needs to read it back. Stores inbox metadata in a tool-neutral state file under .agents/agentmail/ so multiple inboxes survive across sessions. MCP is intentionally NOT recommended — direct REST is simpler and avoids the npx mcp-remote shim. mcporter is documented as a fallback for projects already standardised on MCP tooling.
stevengonsalvez/agents-in-a-box · ★ 14 · AI & Automation · score 71

Install: claude install-skill stevengonsalvez/agents-in-a-box

# agentmail — disposable inboxes for agent workflows ## What this skill gives you The `myagentinbox.com` service hands out 24-hour disposable inboxes via plain REST. Five things to know: | capability | how | |---|---| | Create inbox | `POST /api/inboxes` — returns `{address, created_at, expires_in: "24h"}`. No auth. | | Check inbox exists | `GET /api/inboxes/{address}` | | List messages | `GET /api/inboxes/{address}/messages` — returns `{data: [...]}` | | Read message | `GET /api/inboxes/{address}/messages/{id}` | | Download attachment | `GET /api/inboxes/{address}/messages/{id}/attachments/{filename}` | Limits (per IP): | limit | value | |---|---| | Inbox creation | 3 per minute | | API reads | 20 per minute | | Inbox lifetime | 24 hours then auto-deleted | | Max email size | 10 MB | **No accounts. No keys. No tracking.** Inbox + everything in it vanishes after 24h. Perfect for ephemeral test flows; useless for anything that needs to be retained. ## When to use - Driving `/expect-test`, `/shot-testing`, or any browser test through a signup flow that requires email verification - Capturing a one-time password / magic-link sent by a service the agent is registering with - Receiving a webhook-style email as a stage in an automated pipeline - Pulling an attachment (PDF receipt, exported report) that a service emails out ## When NOT to use - Anything you need to keep — inboxes are gone after 24h - Long-lived account recovery email — pick a real mailbox - Sending email —