analyze-email

analyze-email is a skill for Claude Code from fatbobman/mail-mcp-bridge. It costs 22 tokens per session (1,102 once invoked), scanned A, original, MIT.

A procedure for quickly reviewing one email’s sender, subject, date, contents, and attachments without extracting the attached files.

In plain words
What is it for?
Use it to summarize an email, inspect its metadata, and list attached files from a message ID.
Why use it?
It gives you enough context to decide whether an email needs deeper investigation, without opening or processing every attachment.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the mail-attachment-analyzer plugin — 3 skills, 3 commands shipped together

Good fit Use it to summarize an email, inspect its metadata, and list attached files from a message ID.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fatbobman/mail-mcp-bridge/analyze-email
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.

Any agent
npx skills add fatbobman/mail-mcp-bridge --skill analyze-email
Clone the repo
git clone --depth 1 https://github.com/fatbobman/mail-mcp-bridge

Made for: Claude Code.

Or install mail-attachment-analyzer, the plugin that ships this one along with the rest of its 3 skills, 3 commands.

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 analyze-email

README.md
[![agentmods](https://agentmods.dev/badge/skills/fatbobman/mail-mcp-bridge/analyze-email/github.svg)](https://agentmods.dev/skills/fatbobman/mail-mcp-bridge/analyze-email)
Your own site
<a href="https://agentmods.dev/skills/fatbobman/mail-mcp-bridge/analyze-email"><img src="https://agentmods.dev/badge/skills/fatbobman/mail-mcp-bridge/analyze-email/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.

agentmods 80×15 button for analyze-email

Your own site · 80×15
<a href="https://agentmods.dev/skills/fatbobman/mail-mcp-bridge/analyze-email"><img src="https://agentmods.dev/badge/skills/fatbobman/mail-mcp-bridge/analyze-email.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,102 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00022 $0.01102
Opus 5 $0.00011 $0.00551
Sonnet 5 $0.00004 $0.00220
Haiku 4.5 $0.00002 $0.00110

Measured 11d ago against content hash 13dc4ef19e74, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

analyze-email 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 11d 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.

plugins/mail-attachment-analyzer/skills/analyze-email/SKILL.md · 175 lines

How it starts

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

Analyze Email

Quick analysis of a single email. Read metadata, summarize content, and list attachments without extracting them.

When to Use

Use this skill when you need to:

  • Quickly understand what an email is about
  • Get email metadata (sender, subject, date)
  • See what attachments are included
  • Decide if deeper analysis is needed

Triggers:

English:

  • "Analyze this email <message-id>"
  • "What's in this email <message-id>"
  • "Read this email <message-id>"
  • "Show me this email <message-id>"

Chinese:

  • "分析这封邮件 <message-id>"
  • "这封邮件说什么 <message-id>"
  • "看看这封邮件 <message-id>"
  • "查看邮件内容 <message-id>"

Invocation Methods

Method 1: Natural Language (Recommended)

User: Analyze this email <[email protected]>
AI: [Proceeds to analyze immediately]

Method 2: Slash Command

User: /analyze-email
AI: 请提供要分析的邮件 Message-ID
User: <[email protected]>
AI: [Proceeds to analyze]

Note: When invoked via slash command without parameters, ALWAYS ask for message-id first.

Execution Steps

  1. Get message-id (if not provided)

    Please provide the email Message-ID to analyze
    
    💡 Quick method (recommended):
    In Mail.app: Select email → Press shortcut (⌘⇧C) → Message-ID copied
    See README "Setup Mail Quick Action" section if not configured
    
  2. Read email using MCP

    email_data = mcp__mail__read_email(message_id)
    
  3. Extract key information

    • Sender (from)
    • Recipients (to, cc)
    • Subject
    • Date
    • Body text summary (first 500 chars)
    • Attachments list (filename, type, size)
  4. Present structured output

Output Format

📧 Email Analysis

### Basic Information
- From: [sender email and name]
- To: [recipients]
- CC: [cc recipients if any]
- Subject: [subject line]
- Date: [sent date]

### Content Summary
[First 500 characters of email body, or full text if short]

### 📎 Attachments
[Count] attachment(s):
1. [filename] ([type]) - [size]
2. ...

### 💡 Quick Assessment
- Is this a thread?: Yes/No
- Action required?: Yes/No
- Importance level: High/Medium/Low

Read the full file on GitHub · 175 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. 11d ago First seen · 175 lines · 22 tokens per session scan A 13dc4ef19e74

Subscribe to this mod's changes

analyze-email is a skill published in the GitHub repository fatbobman/mail-mcp-bridge (19 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 1,102 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.