email

A command-based system for managing email, including reading, sending, searching, and organising messages.

In plain words
What is it for?
It is for listing recent, unread, or filtered messages, finding subscriptions, and carrying out other email operations.
Why use it?
It reduces the need to handle common email tasks through separate manual steps.

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/nylas/cli/email
Clone the repo
git clone --depth 1 https://github.com/nylas/cli
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,733 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.00000 $0.04733
Opus 5 $0.00000 $0.02367
Sonnet 5 $0.00000 $0.00947
Haiku 4.5 $0.00000 $0.00473

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

Security

Grade A, and why

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 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.

docs/commands/email.md · 627 lines

How it starts

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

Email Operations

Full email management including reading, sending, searching, and organizing.

List Emails

nylas email list [grant-id]           # List recent emails
nylas email list --limit 20           # Specify number of emails
nylas email list --unread             # Show only unread
nylas email list --starred            # Show only starred
nylas email list --from "[email protected]"  # Filter by sender
nylas email list --metadata key1:value  # Filter by metadata (key1-key5 only)

Example output:

$ nylas email list --limit 5

Recent Emails
─────────────────────────────────────────────────────
  From: John Doe <[email protected]>
  Subject: Meeting Tomorrow
  Date: 2 hours ago
  ID: msg_abc123

  From: GitHub <[email protected]>
  Subject: [repo] New pull request #42
  Date: 5 hours ago
  ID: msg_def456

  From: Newsletter <[email protected]>
  Subject: Weekly Update
  Date: yesterday
  ID: msg_ghi789

Found 5 emails

List Email Subscriptions

Discover mailing-list subscriptions from standard email headers. These commands use the active account, omit postable discussion lists, and never print unsubscribe links. Discovery currently supports Google and Microsoft grants. Nylas does not expose the required original headers for EWS or IMAP messages; see Headers and MIME data.

nylas email subscriptions list                       # Scan 90 days of inbox mail
nylas email subscriptions list --since 180d          # Scan a longer period
nylas email subscriptions list --all-folders         # Include archived and filed mail
nylas email subscriptions list --limit 2000 --json   # Machine-readable output

Unsubscribe

Select subscriptions by the email or List-ID shown by subscriptions list. The command shows the sanitized destination in its review and asks for confirmation. It never deletes existing mail.

nylas email subscriptions unsubscribe [email protected] --dry-run
nylas email subscriptions unsubscribe [email protected]
nylas email subscriptions unsubscribe [email protected] updates.example.com
nylas email subscriptions unsubscribe [email protected] --yes --json

Read the full file on GitHub · 627 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. 2d ago First seen · 627 lines · 0 tokens per session scan A 31f01c727985

Subscribe to this mod's changes

email is a command published in the GitHub repository nylas/cli (68 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,733 tokens. 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.