agentmods.dev

mcp-mailtrap AGENTS.md

mcp-mailtrap AGENTS.md is an instructions file for Codex, OpenCode from pijusz/mcp-mailtrap. It costs 1,336 tokens per session, scanned A, original, MIT.

An instruction guide for using the mcp-mailtrap service to inspect email delivery and engagement. Mailtrap is an email testing and sending service that reports events such as delivery, bounces, opens, and clicks.

In plain words
What is it for?
It helps review delivery statistics, investigate failed messages, compare results by domain or email provider, track opens and clicks over time, and check contact-list hygiene.
Why use it?
It provides a structured way to find why messages were not delivered and where delivery or engagement problems occur. It also helps identify suppressed contacts that still appear on mailing lists.

Instructions file for CodexOpenCode

not rated 3 4mo ago A scan 1,336 tokens original MIT
View the source file pijusz/mcp-mailtrap
Install

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.

agentmods
npx agentmods add instructions/pijusz/mcp-mailtrap/agents-md
Clone the repo
git clone --depth 1 https://github.com/pijusz/mcp-mailtrap

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for mcp-mailtrap AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/pijusz/mcp-mailtrap/agents-md.svg)](https://agentmods.dev/instructions/pijusz/mcp-mailtrap/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/pijusz/mcp-mailtrap/agents-md"><img src="https://agentmods.dev/badge/instructions/pijusz/mcp-mailtrap/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,336 This file is loaded in full into every session.
When invoked 1,336 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01336 $0.01336
Opus 5 $0.00668 $0.00668
Sonnet 5 $0.00267 $0.00267
Haiku 4.5 $0.00134 $0.00134

Measured 5d ago against content hash f5b9e6e5339e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-mailtrap AGENTS.md 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 5d 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.

AGENTS.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

mcp-mailtrap — Agent Guide

Workflow-oriented guide for AI agents using this MCP server.

Authentication

Set MAILTRAP_API_TOKEN env var. Optionally set MAILTRAP_SENDING_TOKEN for transactional/bulk send.api requests and MAILTRAP_ACCOUNT_ID for a default account — otherwise the account is auto-discovered on first tool call.

Workflows

Investigating Deliverability

  1. Start with get_stats for overall delivery/bounce/spam rates
  2. Drill down with get_stats(group_by: "domain") or get_stats(group_by: "esp") to find problem areas
  3. Use get_email_logs with status: "not_delivered" for specific failed emails
  4. Check get_email_log for individual message event timelines

Monitoring Open & Click Rates

  1. Use get_stats for aggregate open/click rates
  2. Use get_stats(group_by: "date") for trends over time
  3. Filter by categories to compare different email types
  4. Use get_stats(group_by: "esp") to identify ESP-specific deliverability issues

Managing Contact Lists

  1. Use list_contact_lists to see available lists
  2. Use check_list_hygiene to find suppressed emails that still belong to contact lists
  3. Follow suggested actions to clean up lists
  4. Use import_contacts for bulk additions, export_contacts for bulk exports
  5. Use manage_contact_field to manage custom fields for segmentation

Testing Emails

  1. Use send_test_email to send to a sandbox inbox (optionally using MAILTRAP_TEST_INBOX_ID / MAILTRAP_DEFAULT_FROM_EMAIL defaults)
  2. Use get_messages to see the email in the inbox
  3. Use analyze_message for combined spam score + HTML compatibility + headers report
  4. Use get_message(format: "htmlsource") to inspect raw HTML
  5. Iterate on email content based on analysis results

Template Management

  1. Use list_templates to see existing templates
  2. Use create_template with body_html for raw HTML templates
  3. For react-email templates: write a component file (.tsx, .jsx, .js, or .mjs), use render_react_email to produce HTML, then create_template
  4. Use send_email with template_uuid to send using the template
  5. Track template performance via get_stats(group_by: "category")

Read the full file on GitHub · 117 lines

Changes

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.

  1. 5d ago First seen · 117 lines · 1,336 tokens per session scan A f5b9e6e5339e

Subscribe to this mod's changes

mcp-mailtrap AGENTS.md is an instructions file published in the GitHub repository pijusz/mcp-mailtrap (3 stars, last pushed 4mo ago), licensed MIT. It adds 1,336 tokens to every session, about $0.0067 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.

Analytics and metrics
Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens