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 aashari/ai-agent-skills --skill mail-threadgit clone --depth 1 https://github.com/aashari/ai-agent-skillsWrote 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/aashari/ai-agent-skills/mail-thread)<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>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.00076 | $0.00730 |
| Opus 5 | $0.00038 | $0.00365 |
| Sonnet 5 | $0.00015 | $0.00146 |
| Haiku 4.5 | $0.00008 | $0.00073 |
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.
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]
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.
- 8d ago First seen · 95 lines · 76 tokens per session scan A ecd27b155fc2
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.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.