An add-on for composing and sending one deliberate email to a named recipient through Resend, using the operator's writing style and saved context. It records the send and applies shared safety checks before sending.

Use it to write a follow-up, introduction, proposal, or other one-off email, optionally revise the draft, and send it to the specified recipient.

It keeps drafting, approval-related checks, sending, and audit logging in one controlled workflow. It is intended for a single purposeful message, not bulk or cold outreach.

send-email — Skill for Claude Code and Codex by aeonfun/aeon

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 aeonfun/aeon --skill send-email

Clone the repo

git clone --depth 1 https://github.com/aeonfun/aeon

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/aeonfun/aeon/send-email/github.svg)](https://agentmods.dev/skills/aeonfun/aeon/send-email)

Your own site

<a href="https://agentmods.dev/skills/aeonfun/aeon/send-email"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/send-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aeonfun/aeon/send-email"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/send-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 3,407 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Data Exfiltration · line 99
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
medium Data Exfiltration · line 99
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.03407
Opus 5.5	$0.00016	$0.01363
Sonnet 5.5	$0.00008	$0.00681
Haiku 4.5	$0.00004	$0.00341

Measured 17d ago against content hash f959fd69340f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

send-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 17d 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

Copies of this mod

1 near-identical copy found in the catalogue:

send-email — 100% identical, 0 lines differ

skills/send-email/SKILL.md · 135 lines

How it starts

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

${var} — who to email and why, e.g. [email protected] | subject=Intro | about=propose a 20-min call on X. Freeform also works ("email [email protected] to follow up on yesterday's demo"). cc= is optional. The reply-shape revise:<instruction> (Telegram force-reply, e.g. revise:make it warmer) refines the last composed draft for review only — it never sends.

Read soul/ (for voice) and memory/MEMORY.md (for context) before composing.

What this does

Composes a single, purposeful email and sends it in-run via Resend (./secretcurl), gated by the shared send caps + kill-switch and logged to the shared ledger memory/email-log.json. The send is irreversible, so it's the skill's final action, behind a set of fail-closed checks (see "Send (in-run)" below): a skipped or failed check means do not send, never send anyway. This is the general-purpose sibling of vuln-scanner's disclose arm (Arm C, var=disclose) — same caps + audit CC, any recipient and purpose instead of only vuln maintainers.

This is not a bulk or cold-outreach tool. One deliberate recipient per run, with a genuine reason to write. If the request reads as mass-mailing, list-blasting, or spam, refuse and log SEND_EMAIL_REFUSED: not a 1:1 purposeful email.

Steps

Revise intercept (Telegram force-reply — re-stage for review only, NEVER auto-send)

Before anything else, if ${var} starts with revise:, the operator replied to a "refine this email?" prompt. Handle it here and end the run — the normal compose/send flow below does NOT run, and nothing is ever sent:

Strip the prefix. The instruction is ${var#revise:} (keep any inner colons), e.g. make it warmer, shorten to 3 lines, drop the meeting ask.
Load the last draft from memory/drafts/send-email-latest.md (the review copy the normal run saves in step 4). If it's missing or empty, there's nothing to refine: send ./notify "Nothing to revise yet — compose an email first, then reply here to refine it." and end the run.
Regenerate the email applying the instruction — re-read soul/ for voice; keep the same recipient / cc / subject unless the instruction changes them; keep the body as the exact send-ready text (operator-only notes stay out).
Re-stage for REVIEW ONLY. Overwrite memory/drafts/send-email-latest.md with the revised draft. Do NOT run the Send step. A revise: reply never sends — the operator confirms a real send by invoking send-email normally (which re-composes and sends in-run).
Notify the operator with the full revised draft for review — multi-line ⇒ ./notify -f <file>:
```
revised draft (not sent) → <to>: <subject>

<body>
```

Re-offer a further revision (the operator is iterating — skip the daily dedup guard here):

./notify "Want another pass? Reply with a change and I'll revise the draft again (still won't send)." \
  --force-reply --placeholder "e.g. make it warmer" \
  --context "send-email::revise"

Log - SEND_EMAIL_REVISED (draft re-staged for review, not sent) under a ### send-email heading in memory/logs/${today}.md, then end the run.

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

17d ago Changed f959fd69340f
22d ago Changed a70138d1a268
1mo ago Changed · +2 lines da2ac8b88d22
1mo ago First seen · 133 lines · 39 tokens per session scan A 67d4c34d7fcd

Subscribe to this mod's changes

send-email is a skill published in the GitHub repository aeonfun/aeon (783 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 3,407 once invoked, about $0.0002 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-09-05.

Claude Code Productivity agent-framework agents ai ai-agents anthropic

octopus-quick

Quick execution for ad-hoc tasks without workflow overhead. Use when: Use this skill when user says "quick fix", "ad-hoc task", or explicitly. requests fast execution without full workflow overhead.

CES-Ltd/Lumi · 46 tokens

skill-creator

Create new reusable skills from conversation context.

vstorm-co/pydantic-deepagents · 11 tokens

caveman-help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

stevesolun/ctx · 56 tokens

flowcraft-config

Author, validate, and troubleshoot complete FlowCraft configuration: deployment documents (deploy.yaml with the runtime section, inference/workspace/sandbox/tool sub-documents, core/memory contracts, and graph JSON node wiring), craft.yaml application definitions, and plugin.json manifests. Use when writing or…

GizClaw/flowcraft · 121 tokens

skill-factory

A workflow that examines completed session work and turns reusable patterns into Claude Code skills.

sangrokjung/claude-forge · 122 tokens

toolbox

Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…

stevesolun/ctx · 77 tokens