mail-thread

mail-thread is a skill for Claude Code from aashari/ai-agent-skills. It costs 76 tokens per session (730 once invoked), scanned A, original, MIT.

A tool for reading and summarizing a complete email conversation. An email thread is a sequence of replies about the same subject, shown in order with the participants and decisions.

In plain words
What is it for?
Use it to catch up on a conversation, inspect a thread by subject or message row number, and understand who said what.
Why use it?
It saves you from opening and piecing together every message yourself. The summary helps clarify how the discussion developed and what was agreed.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; built for openclaw.

Good fit Use it to catch up on a conversation, inspect a thread by subject or message row number, and understand who said what.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aashari/ai-agent-skills/mail-thread
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 aashari/ai-agent-skills --skill mail-thread
Clone the repo
git clone --depth 1 https://github.com/aashari/ai-agent-skills

Made for: Claude Code.

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 mail-thread

README.md
[![agentmods](https://agentmods.dev/badge/skills/aashari/ai-agent-skills/mail-thread.svg)](https://agentmods.dev/skills/aashari/ai-agent-skills/mail-thread)
Your own site
<a href="https://agentmods.dev/skills/aashari/ai-agent-skills/mail-thread"><img src="https://agentmods.dev/badge/skills/aashari/ai-agent-skills/mail-thread.svg" alt="Measured on agentmods" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 730 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.00076 $0.00730
Opus 5 $0.00038 $0.00365
Sonnet 5 $0.00015 $0.00146
Haiku 4.5 $0.00008 $0.00073

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

Security

Grade A, and why

mail-thread 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 8d 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.

skills/apple-mail/mail-thread/SKILL.md · 95 lines

How it starts

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

Mail Thread — Read a Full Email Conversation

Thread: $ARGUMENTS

Step 1: Find the thread

Option A: Search by subject keyword

DB="$HOME/Library/Mail/V10/MailData/Envelope Index"
QUERY="<extracted from $ARGUMENTS>"

sqlite3 "$DB" "
SELECT m.ROWID, m.conversation_id, s.subject,
       datetime(m.date_received,'unixepoch','localtime') as dt,
       a.address as sender
FROM messages m
JOIN subjects  s ON m.subject = s.ROWID
JOIN addresses a ON m.sender  = a.ROWID
WHERE s.subject LIKE '%${QUERY}%' AND m.deleted=0
ORDER BY m.date_received DESC LIMIT 10;" 2>/dev/null

Option B: If ROWID provided directly

sqlite3 "$DB" "
SELECT conversation_id FROM messages WHERE ROWID = <ROWID>;" 2>/dev/null

Step 2: Get all messages in the thread by conversation_id

CONV_ID=<from step 1>

sqlite3 "$DB" "
SELECT m.ROWID,
       datetime(m.date_received,'unixepoch','localtime') as dt,
       a.address as sender, a.comment as name,
       s.subject, mb.url as mailbox, m.read
FROM messages m
JOIN subjects  s  ON m.subject = s.ROWID
JOIN addresses a  ON m.sender  = a.ROWID
JOIN mailboxes mb ON m.mailbox = mb.ROWID
WHERE m.conversation_id = ${CONV_ID}
  AND m.deleted = 0
ORDER BY m.date_received ASC;" 2>/dev/null

Step 3: Read all message bodies

python3 ~/.claude/skills/_mail-shared/parser.py <ROWID1> <ROWID2> <ROWID3> ...

Step 4: Reconstruct the conversation

Present chronologically:

  • Who sent each message and when
  • Key content of each message (summarize long ones, quote short ones)
  • Reply chain structure

Step 5: Summarize the thread

After showing the conversation:

  • What was the original question/issue?
  • What was discussed/debated?
  • What was decided or concluded?
  • Are there any open questions or pending actions?
  • Who is waiting on whom?

Output Format

Thread: [Subject] [N messages | started: date | participants: list]


[Date] [Sender Name] [→ Reply to: ...]

[message content, summarized if long]

Read the full file on GitHub · 95 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. 8d ago First seen · 95 lines · 76 tokens per session scan A ecd27b155fc2

Subscribe to this mod's changes

mail-thread is a skill published in the GitHub repository aashari/ai-agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 76 tokens to every session and 730 once invoked, about $0.0004 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.