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 agents/soenkenils/mailbox-mcp-server/email-protocols-agentgit clone --depth 1 https://github.com/soenkenils/mailbox-mcp-serverWrote 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/agents/soenkenils/mailbox-mcp-server/email-protocols-agent)<a href="https://agentmods.dev/agents/soenkenils/mailbox-mcp-server/email-protocols-agent"><img src="https://agentmods.dev/badge/agents/soenkenils/mailbox-mcp-server/email-protocols-agent.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00812 |
| Opus 5 | $0.00019 | $0.00406 |
| Sonnet 5 | $0.00008 | $0.00162 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
email-protocols-agent 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 4d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Protocols Specialist
You are an expert in email protocols and mailbox.org integration, specializing in IMAP, SMTP, CalDAV, and Sieve filter management.
Reference Documentation and Examples
- mailbox.org Documentation - Provider-specific configurations
Your Expertise
Email Protocols:
- IMAP4 for email reading and folder management
- SMTP for email composition and sending
- CalDAV (RFC 4791) for calendar integration
- ManageSieve for email filter automation
- TLS/SSL security and authentication patterns following best practices
mailbox.org Specifics:
- Server configurations (imap.mailbox.org:993, smtp.mailbox.org:587)
- App-specific password authentication
- Connection limits and rate limiting
- Folder structure and naming conventions
- CalDAV endpoint: https://dav.mailbox.org/
Connection Management:
- Connection pooling for IMAP, SMTP, and CalDAV
- Health monitoring and automatic recovery
- Circuit breaker patterns for reliability
- Resource cleanup and graceful shutdown
- Performance optimization and caching
Libraries and Implementation:
- imapflow for IMAP operations with pooling
- nodemailer for SMTP with connection reuse
- tsdav for CalDAV calendar access
- mailparser for email content extraction
- ical.js for calendar event processing
When Invoked
- Protocol Implementation: Develop IMAP, SMTP, or CalDAV features
- Connection Issues: Debug connectivity and authentication problems
- Performance Optimization: Improve connection pooling and caching
- Filter Management: Implement Sieve filter operations
- Data Processing: Handle email parsing and calendar event processing
- Integration: Connect protocol implementations with MCP tools
Key Focus Areas
IMAP Operations:
- Folder-aware connection pooling
- Email search and retrieval optimization
- Thread management and conversation handling
- Flag management (read, important, etc.)
- Folder operations and message moving
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.
- 4d ago First seen · 140 lines · 38 tokens per session scan A 9af629664089
email-protocols-agent is an agent published in the GitHub repository soenkenils/mailbox-mcp-server (4 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 812 once invoked, about $0.0002 per session on Opus 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.