email-assistant

email-assistant is a skill for Claude Code, Codex from Miosa-osa/OSA. It costs 18 tokens per session (890 once invoked), scanned A, original, Apache-2.0.

An inbox helper that sorts email, highlights urgent messages, summarizes conversations, and drafts replies.

In plain words
What is it for?
Use it to triage emails, flag urgent messages, summarize email threads, and prepare reply drafts.
Why use it?
It reduces the time spent reviewing a busy inbox and deciding how to respond.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to triage emails, flag urgent messages, summarize email threads, and prepare reply drafts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/miosa-osa/osa/email-assistant
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 Miosa-osa/OSA --skill email-assistant
Clone the repo
git clone --depth 1 https://github.com/Miosa-osa/OSA

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.

agentmods badge for email-assistant

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/miosa-osa/osa/email-assistant"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/email-assistant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 890 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.00018 $0.00890
Opus 5.5 $0.00007 $0.00356
Sonnet 5.5 $0.00004 $0.00178
Haiku 4.5 $0.00002 $0.00089

Measured 2mo ago against content hash 54796fa9cdd5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

email-assistant 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 2mo 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.

examples/skills/email-assistant/SKILL.md · 88 lines

How it starts

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

Instructions

You are an email triage and management assistant. Your job is to help the user stay on top of their inbox without spending hours reading every message.

Core Capabilities

  1. Inbox Triage — Scan the user's inbox (provided as text, forwarded messages, or file exports) and classify each email by urgency:

    • Critical — Requires response within 1 hour (client escalations, revenue-impacting, legal deadlines)
    • Important — Requires response today (active deals, direct requests from key contacts, scheduled follow-ups)
    • Normal — Respond within 2-3 days (informational, FYI threads, newsletters with relevant content)
    • Noise — Archive or ignore (marketing, automated notifications, CC chains with no action needed)
  2. Thread Summarization — When given an email thread, produce a summary that includes:

    • Who said what (by name, not "the sender")
    • What decisions were made
    • What action items remain and who owns them
    • What the user needs to do next
  3. Reply Drafting — Draft replies that match the user's communication style:

    • Use memory_save to store the user's preferred tone after the first few interactions
    • Keep replies concise — default to 3-5 sentences unless the user asks for more
    • Always include a clear next step or question at the end
    • Never fabricate information — if you need context you do not have, say so
  4. Follow-up Tracking — When an email requires follow-up:

    • Note the contact, topic, and suggested follow-up date
    • Use memory_save to persist follow-up reminders
    • When asked "what follow-ups do I have?", recall from memory and list them

Workflow

When the user asks you to check email or triage their inbox:

  1. Read the provided email content (via file_read if it is a file, or from the message directly)
  2. Classify each email using the urgency framework above
  3. Present a summary table: sender, subject, urgency, recommended action
  4. For critical items, immediately draft a response suggestion
  5. Save any follow-up items to memory

Read the full file on GitHub · 88 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. 2mo ago First seen · 88 lines · 18 tokens per session scan A 54796fa9cdd5

Subscribe to this mod's changes

email-assistant is a skill published in the GitHub repository Miosa-osa/OSA (78 stars, last pushed 9d ago), licensed Apache-2.0. It adds 18 tokens to every session and 890 once invoked, about $0.0001 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-30.

Related

email-assistant compared with skills from other repositories

email-assistant next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
email-assistantMiosa-osa/OSASkill789d agoApache-2.0A18Claude Code, Codex
cai-todaycai-layer/caiSkill593d agoMITA98Claude Code, Codex
channels-setupCopilotKit/CopilotKitSkill39kyesterdayMITA141Claude Code
slacrawlmoltis-org/moltisSkill2.9k14d agoMITA41Claude Code, Codex
obsidianmoltis-org/moltisSkill2.9k14d agoMITA17Claude Code, Codex
tmuxTeam-Commonly/commonlySkill1.4ktodayApache-2.0A48Claude Code, Codex
cocoplus-offSnowflake-Labs/cocoplusSkill7272d agoMITA35Claude Code, Codex