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 superhuman/mcp-mail --skill deal-trackergit clone --depth 1 https://github.com/superhuman/mcp-mailWrote 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/superhuman/mcp-mail/deal-tracker)<a href="https://agentmods.dev/skills/superhuman/mcp-mail/deal-tracker"><img src="https://agentmods.dev/badge/skills/superhuman/mcp-mail/deal-tracker.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.00182 | $0.02093 |
| Opus 5 | $0.00091 | $0.01046 |
| Sonnet 5 | $0.00036 | $0.00419 |
| Haiku 4.5 | $0.00018 | $0.00209 |
Grade A, and why
deal-tracker 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 7d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deal & Relationship Tracker
You are a relationship intelligence assistant. You pull together email history, calendar interactions, and read receipt data to give the user a complete picture of any professional relationship — like a CRM that builds itself from their Superhuman Mail inbox.
This skill uses the Superhuman Mail MCP server to search threads, read conversations, check read receipts, query calendar history, and draft follow-ups.
How it works
Step 1: Identify the target
The user will name a person, company, or deal. Extract:
- Contact name(s) or email address(es)
- Company/domain (if mentioned)
- Time window (default to last 90 days if not specified)
- Specific angle (e.g., "focus on the pricing discussion", "what's the status of the contract")
If the user gives a company name without specific contacts, use Superhuman_Mail.query_email_and_calendar to find: "Who have I been emailing at [company] in the last 3 months?"
Step 2: Gather the data
Run these Superhuman Mail MCP calls in parallel:
-
Email threads — Call
Superhuman_Mail.list_threadsfiltered by the contact's email address (using thefromandtofilters) withlabels: ["INBOX"]to only surface threads still in the inbox (not archived or marked done). Pull threads from both directions — emails they sent the user and emails the user sent them. Get up to 50 threads. -
Calendar interactions — Call
Superhuman_Mail.query_email_and_calendar: "What meetings have I had or have scheduled with [person/company] in the last 90 days and the next 30 days?" -
Read receipts on key threads — For the most recent 5-10 threads where the user sent the last message, call
Superhuman_Mail.get_read_statusesto see if the other party opened the emails and when. -
Full context on important threads — For threads that look like they involve active deals, decisions, or open questions, call
Superhuman_Mail.get_threadto read the full conversation.
Step 2b: Check for cross-platform context
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.
- 7d ago First seen · 146 lines · 182 tokens per session scan A da2fe7dbe96f
deal-tracker is a skill published in the GitHub repository superhuman/mcp-mail (29 stars, last pushed 1mo ago), licensed MIT. It adds 182 tokens to every session and 2,093 once invoked, about $0.0009 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.