himalaya-email

himalaya-email is a skill for Claude Code from isaacrowntree/claude-social-skills. It costs 39 tokens per session (1,301 once invoked), scanned A, original, MIT.

A command-line email tool for reading, searching, sending, and managing messages. It can also show email headers, which contain technical details about a message's route and origin.

In plain words
What is it for?
Use it to list inbox or sent mail, read messages, search available messages, inspect headers, and manage email.
Why use it?
It lets the coding agent work with email from the terminal instead of requiring a separate mail application. Preview options can help inspect messages without marking them as read.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the himalaya-email plugin — 1 skill shipped together

Good fit Use it to list inbox or sent mail, read messages, search available messages, inspect headers, and manage email.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/isaacrowntree/claude-social-skills/himalaya-email
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 isaacrowntree/claude-social-skills --skill himalaya-email
Clone the repo
git clone --depth 1 https://github.com/isaacrowntree/claude-social-skills

Made for: Claude Code.

Or install himalaya-email, the plugin that ships this one along with the rest of its 1 skill.

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 himalaya-email

README.md
[![agentmods](https://agentmods.dev/badge/skills/isaacrowntree/claude-social-skills/himalaya-email/github.svg)](https://agentmods.dev/skills/isaacrowntree/claude-social-skills/himalaya-email)
Your own site
<a href="https://agentmods.dev/skills/isaacrowntree/claude-social-skills/himalaya-email"><img src="https://agentmods.dev/badge/skills/isaacrowntree/claude-social-skills/himalaya-email/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.

agentmods 80×15 button for himalaya-email

Your own site · 80×15
<a href="https://agentmods.dev/skills/isaacrowntree/claude-social-skills/himalaya-email"><img src="https://agentmods.dev/badge/skills/isaacrowntree/claude-social-skills/himalaya-email.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,301 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.00039 $0.01301
Opus 5 $0.00019 $0.00651
Sonnet 5 $0.00008 $0.00260
Haiku 4.5 $0.00004 $0.00130

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

Security

Grade A, and why

himalaya-email 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 12d 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.

plugins/himalaya-email/skills/himalaya-email/SKILL.md · 138 lines

How it starts

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

Himalaya Email CLI

Use himalaya (v1.2.0) for all email operations. The user's account should be configured in ~/Library/Application Support/himalaya/config.toml.

When to Use

  • User asks about emails, inbox, or messages
  • User wants to read, search, or list emails
  • User wants to trace email origin or check headers
  • User mentions a sender or subject and wants to find/read the email

Core Commands

# List recent emails (default: INBOX)
himalaya envelope list --page-size 20

# List emails in a specific folder
himalaya envelope list --folder "Sent" --page-size 20

# Read an email by ID (marks as seen)
himalaya message read <ID>

# Read without marking as seen (preview mode)
himalaya message read -p <ID>

# Read with no headers (body only)
himalaya message read --no-headers <ID>

# Read with specific headers visible
himalaya message read -H "From" -H "To" -H "Subject" -H "Date" <ID>

# Search/filter envelopes (if supported by backend)
himalaya envelope list --page-size 50

Tracing Email Origin / Headers

When the user wants to know where an email came from, read it with authentication headers:

himalaya message read -p \
  -H "From" \
  -H "Reply-To" \
  -H "Return-Path" \
  -H "Received" \
  -H "X-Originating-IP" \
  -H "Authentication-Results" \
  -H "Received-SPF" \
  -H "DKIM-Signature" \
  -H "ARC-Authentication-Results" \
  -H "Message-ID" \
  -H "X-Mailer" \
  <ID>

How to Interpret Headers

  • SPF (Sender Policy Framework): spf=pass means the sending IP is authorized by the domain. Look for the IP in Received-SPF.
  • DKIM (DomainKeys Identified Mail): dkim=pass means the email signature is valid and the content wasn't tampered with. Check header.d= for the signing domain.
  • DMARC: dmarc=pass means the domain's SPF/DKIM alignment policy passed.
  • ARC (Authenticated Received Chain): Shows authentication survived forwarding.
  • Return-Path: The actual envelope sender (where bounces go).
  • Received headers: Read bottom-to-top to trace the email's path through servers.
  • Message-ID: Unique identifier; the domain after @ often reveals the originating mail system.
  • X-Originating-IP: If present, the sender's actual IP address.

Read the full file on GitHub · 138 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. 12d ago First seen · 138 lines · 39 tokens per session scan A ac790d4552b6

Subscribe to this mod's changes

himalaya-email is a skill published in the GitHub repository isaacrowntree/claude-social-skills (4 stars, last pushed 12d ago), licensed MIT. It adds 39 tokens to every session and 1,301 once invoked, about $0.0002 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.

Related

Other skills, from other repositories