| name | agent-email-inbox |
| description | Use when setting up a secure email inbox for any AI agent — configuring inbound email via Resend, webhooks, tunneling for local development, and implementing security measures to prevent prompt injection attacks. Also use when someone mentions 'agent email', 'bot inbox', 'receive emails for agent', 'agent webhook', 'email security for AI', 'prompt injection via email', 'inbound email for bot', or wants their AI agent to receive and respond to emails securely.
|
AI Agent Email Inbox
Set up a secure email inbox that lets an AI agent receive and respond to emails, with protection against prompt injection and email-based attacks.
Core principle: An AI agent's inbox is a potential attack vector. Malicious actors can email instructions that the agent might blindly follow. Security configuration is not optional — it's the first thing you implement, not the last.
This skill is context-independent — it does not use brand/ files and works identically in any project.
On Activation
- Ask the user which agent needs an email inbox and what framework they're using (Next.js, Express, etc.).
- Determine environment: local development or production deployment.
- Walk through domain setup (Resend-managed or custom).
- Set up webhook endpoint with signature verification.
- If local dev: configure tunneling.
- Implement security level — read references/security-levels.md and present options to the user.
- Connect webhook to agent processing.
Output: A configured webhook handler file, environment variable checklist, and security configuration.
Architecture
Sender → Email → Resend (MX) → Webhook → Your Server → AI Agent
↓
Security Validation
↓
Process or Reject
