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 shippy/personal-intelligence-kit --skill email-analyzergit clone --depth 1 https://github.com/shippy/personal-intelligence-kitWrote 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/shippy/personal-intelligence-kit/email-analyzer)<a href="https://agentmods.dev/skills/shippy/personal-intelligence-kit/email-analyzer"><img src="https://agentmods.dev/badge/skills/shippy/personal-intelligence-kit/email-analyzer/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.
<a href="https://agentmods.dev/skills/shippy/personal-intelligence-kit/email-analyzer"><img src="https://agentmods.dev/badge/skills/shippy/personal-intelligence-kit/email-analyzer.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.00421 |
| Opus 5.5 | $0.00018 | $0.00168 |
| Sonnet 5.5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
email-analyzer 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 1mo 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.
What it actually says
Email Analyzer
Query your notmuch-indexed email archive. Used by other skills or directly.
Invocation
Direct use via notmuch CLI is fastest, but this skill provides helpful wrappers:
cd .claude/skills/email-analyzer
uv run query.py "date:7d.. tag:sent" # Last week's sent mail
uv run query.py --recent 20 # 20 most recent messages
uv run query.py --from "[email protected]" # From a specific sender
uv run query.py --stats # Volume stats
What It Does
Wraps notmuch search and notmuch show with conveniences:
- Filters out bulk/newsletter senders heuristically
- Extracts "human" messages (has personal tone, not auto-generated)
- Formats results as markdown for piping into other skills
Example: Human Messages Only
uv run query.py --human date:7d..
Filters:
- Skips messages with
unsubscribein the body - Skips messages from
noreply@/notifications@senders - Prefers messages with salutations (
Hi {{ owner_name }}, etc.)
Used By
cross-source-queries/commitments.py— scans sent mail for promisesweekly-reflection/weekly_reflection.py— extracts recent subjects- Ad-hoc:
/briefing: Alice— gather all Alice-related messages
Requirements
notmuchinstalled and indexed (seeemail-ingest)- Email source enabled in
vault.toml
Philosophy
Email is a graph of relationships, not a to-do list. This skill treats it as such: filter noise, surface signal, find the humans.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 54 lines · 45 tokens per session scan A 58d7a1e0102b
email-analyzer is a skill published in the GitHub repository shippy/personal-intelligence-kit (14 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 421 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.