An evidence-based workflow for handling real email accounts, including sorting messages, drafting replies, sending mail, and checking that a message appears in Sent.

Use it to triage inboxes, archive low-value mail, draft or send messages, verify sent messages, and route investor, billing, research, or knowledge-capture work appropriately.

It reduces mistakes such as using the wrong account, claiming an email was sent without proof, or handling a billing or customer thread without the right supporting workflow.

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

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 Jamkris/everything-gemini-code --skill email-ops

Clone the repo

git clone --depth 1 https://github.com/Jamkris/everything-gemini-code

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/jamkris/everything-gemini-code/email-ops/github.svg)](https://agentmods.dev/skills/jamkris/everything-gemini-code/email-ops)

Your own site

<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/email-ops"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/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/jamkris/everything-gemini-code/email-ops"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/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 762 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 92% 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.00762
Opus 5.5	$0.00020	$0.00305
Sonnet 5.5	$0.00010	$0.00152
Haiku 4.5	$0.00005	$0.00076

Measured 1mo ago against content hash 0f48302235ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

This is a copy

92% identical to email-ops — 27 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.

skills/email-ops/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 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 · 122 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.

1mo ago First seen · 122 lines · 50 tokens per session scan A 0f48302235ff

Subscribe to this mod's changes

email-ops is a skill published in the GitHub repository Jamkris/everything-gemini-code (91 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 762 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to email-ops, differing in 27 lines, and is treated as a copy.

Productivity Writing and docs ai-agents antigravity developer-tools gemini-cli gemini-cli-extension gemini-cli-skills

ciel-antigravity-lookup

Find Antigravity conversations on macOS by UUID or keyword.

jxoesneon/Ciel · 21 tokens

persistence

Continue working on a task until completion with automatic retry, self-verification, and alternative approaches. Activates "ralph mode" - never give up until the goal is achieved or explicitly impossible. Use when tasks require tenacity and iteration.

richardcb/oh-my-gemini · 52 tokens

email-ops