mailgraph

A command that builds a graph showing who sent messages to whom from email files or a BBS message dump. A graph represents people or addresses as points and messages between them as connections.

In plain words
What is it for?
Use it to inspect contacts, group messages into subject threads, combine email aliases, or export the result as SVG, JSON, or DOT.
Why use it?
It derives connections directly from From and To headers, so the relationships do not depend on an AI interpretation.

Command

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 commands/esaruoho/apple/mailgraph
Clone the repo
git clone --depth 1 https://github.com/esaruoho/apple
Per session 74 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 192 The whole file, excluding the scripts and references it only reads on demand.
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.00074 $0.00192
Opus 5 $0.00037 $0.00096
Sonnet 5 $0.00015 $0.00038
Haiku 4.5 $0.00007 $0.00019

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

Security

Grade A, and why

mailgraph 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 2d 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.

commands/mailgraph.md · 15 lines

What it actually says

Build a mail/contacts graph from any folder of messages. Parses From:/To: headers directly — the addressing IS the edge.

/Users/esaruoho/work/apple/bin/mailgraph $ARGUMENTS

Examples:

  • /mailgraph --dir ~/Downloads/SomeBBS --svg /tmp/g.svg then it opens
  • /mailgraph --dir <maildir> --threads (subject-line threads)
  • /mailgraph --dir <maildir> --alias "[email protected]=Bill Beaty"
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. 2d ago First seen · 15 lines · 0 tokens per session scan A 8ac7680659cb

Subscribe to this mod's changes

mailgraph is a command published in the GitHub repository esaruoho/apple (11 stars, last pushed 5d ago), licensed MIT. It adds 74 tokens to every session and 192 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-30.