A workflow for handling real email inboxes, including sorting messages, drafting replies, sending mail, and checking that sent messages actually appear in the Sent folder.

Use it to triage inboxes, draft or reply to messages, send approved email, verify delivery records, and capture important conversations for later reference.

It reduces mistakes in mailbox work, especially when several accounts, threads, or follow-ups are involved.

email-ops — Skill for Claude Code and Codex by nklofy

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 nklofy/code-agent-skills --skill email-ops

Clone the repo

git clone --depth 1 https://github.com/nklofy/code-agent-skills

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nklofy/code-agent-skills/email-ops/github.svg)](https://agentmods.dev/skills/nklofy/code-agent-skills/email-ops)

Your own site

<a href="https://agentmods.dev/skills/nklofy/code-agent-skills/email-ops"><img src="https://agentmods.dev/badge/skills/nklofy/code-agent-skills/email-ops/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nklofy/code-agent-skills/email-ops"><img src="https://agentmods.dev/badge/skills/nklofy/code-agent-skills/email-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 765 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 89% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.00765
Opus 5	$0.00025	$0.00382
Sonnet 5	$0.00010	$0.00153
Haiku 4.5	$0.00005	$0.00076

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

Security

Grade A, and why

email-ops 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 5d 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.

Origin

This is a copy

89% identical to email-ops — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

affaan-m-ECC/email-ops/SKILL.md · 123 lines

How it starts

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

Email Ops

Use this when the real task is mailbox work: triage, drafting, replying, sending, or proving a message landed in Sent.

This is not a generic writing skill. It is an operator workflow around the actual mail surface.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

brand-voice before drafting anything user-facing
investor-outreach for investor, partner, or sponsor-facing mail
customer-billing-ops when the thread is a billing/support incident rather than generic correspondence
knowledge-ops when the message or thread should be captured into durable context afterward
research-ops when a reply depends on fresh external facts

When to Use

user asks to triage inbox or archive low-signal mail
user wants a draft, reply, or new outbound email
user wants to know whether a mail was already sent
the user wants proof of which account, thread, or Sent entry was used

Guardrails

draft first unless the user clearly asked for a live send
never claim a message was sent without a real Sent-folder or client-side confirmation
do not switch sender accounts casually; choose the account that matches the project and recipient
do not delete uncertain business mail during cleanup
if the task is really DM or iMessage work, hand off to messages-ops

Workflow

1. Resolve the exact surface

Before acting, settle:

which mailbox account
which thread or recipient
whether the task is triage, draft, reply, or send
whether the user wants draft-only or live send

2. Read the thread before composing

If replying:

read the existing thread
identify the last outbound touch
identify any commitments, deadlines, or unanswered questions

If creating a new outbound:

identify warmth level
select the correct channel and sender account
pull brand-voice before drafting

3. Draft, then verify

For draft-only work:

produce the final copy
state sender, recipient, subject, and purpose

Read the full file on GitHub · 123 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.

5d ago First seen · 123 lines · 50 tokens per session scan A 627bc4a72c07

Subscribe to this mod's changes

email-ops is a skill published in the GitHub repository nklofy/code-agent-skills (19 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 765 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to email-ops, differing in 28 lines, and is treated as a copy.

Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

the-open-agent/openagent · 17 tokens

mochi-remind

Handle due reminders — notify the user with natural language and mark them done.

kirodotdev/KiroCrew · 20 tokens