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 skills add n24q02m/better-email-mcp --skill follow-upgit clone --depth 1 https://github.com/n24q02m/better-email-mcpWrote 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/skills/n24q02m/better-email-mcp/follow-up)<a href="https://agentmods.dev/skills/n24q02m/better-email-mcp/follow-up"><img src="https://agentmods.dev/badge/skills/n24q02m/better-email-mcp/follow-up/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/n24q02m/better-email-mcp/follow-up"><img src="https://agentmods.dev/badge/skills/n24q02m/better-email-mcp/follow-up.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00020 | $0.00612 |
| Opus 5 | $0.00010 | $0.00306 |
| Sonnet 5 | $0.00004 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
follow-up 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 12d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow-Up
Find emails that need follow-up and draft contextual responses.
Unanswered Sent Emails
Find emails you sent that received no reply after N days:
-
Search Sent folder for emails sent N+ days ago:
messages(action="search", query="SINCE 2026-03-16 BEFORE 2026-03-20", folder="Sent", account="...") -
Cross-reference Inbox for replies:
- For each sent email, search Inbox for matching Subject (with
Re:prefix):messages(action="search", query="SUBJECT \"Re: <original subject>\" FROM <recipient>") - If no matching reply found, this email needs follow-up
- For each sent email, search Inbox for matching Subject (with
-
Present candidates with context:
No reply after 5 days: 1. "API Integration Proposal" to [email protected] (sent Mar 18) Original: Asked about timeline for API access 2. "Invoice #2024-003" to [email protected] (sent Mar 16) Original: Sent invoice, requested payment confirmation
Flagged but Unreplied
Find received emails you flagged/starred but never responded to:
messages(action="search", query="FLAGGED", account="...")
Then for each flagged email, check Sent folder for a reply with matching subject. If none found, it needs attention.
Drafting Follow-Up Messages
For each follow-up candidate:
-
Read the original thread to get full context
-
Decide reply type:
- If original was your sent email with no reply: draft a gentle follow-up referencing the original
- If original was received and you haven't replied: draft a response to their message
-
Use reply (not new message) when following up on existing threads:
messages(action="reply", uid="<original_uid>", body="<follow-up text>")Use
messages(action="new")for new conversations. -
Follow-up tone guidelines:
- First follow-up (3-5 days): "Just checking in on this..."
- Second follow-up (7-10 days): "Wanted to circle back on..."
- Final follow-up (14+ days): Direct ask with deadline: "Could you confirm by Friday?"
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.
- 12d ago First seen · 78 lines · 20 tokens per session scan A 9c1f0b6d1199
follow-up is a skill published in the GitHub repository n24q02m/better-email-mcp (34 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 612 once invoked, about $0.0001 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-30.
Other skills, from other repositories
mail-operations
Use this skill whenever the user wants to interact with email. This includes reading inbox, sending emails, replying, searching messages, managing labels and categories, downloading attachments, setting up auto-reply rules, or triggering agents to handle incoming emails. Supports Gmail, Outlook, and IMAP/SMTP (QQ…
imap-smtp-email
Read, search, and manage email via IMAP protocol. Send email via SMTP. Supports Gmail, Outlook, 163.com, 126.com, QQ Mail, and any standard IMAP/SMTP server with multi-account support.
mailbox
A command-line email tool for reading, searching, sending, and managing messages in Gmail, QQ, 163, Outlook, and other IMAP/SMTP accounts.
Run the external email CLI through exec for real IMAP/SMTP/Notmuch mailboxes. Use when the user explicitly wants a real terminal email workflow instead of the built-in benchmark email surfaces.
himalaya
CLI to manage emails via IMAP/SMTP. Use himalaya to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
safe-email-operations
Use email through the bundled mcp-email-server MCP server, diagnose bounded non-secret state, and hand account or credential setup to a user-operated CLI or authenticated local UI.