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.
npx agentmods add skills/aaronjmars/aeon-agent/send-emailnpx skills add aaronjmars/aeon-agent --skill send-emailgit clone --depth 1 https://github.com/aaronjmars/aeon-agentWrote 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.
[](https://agentmods.dev/skills/aaronjmars/aeon-agent/send-email)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/send-email"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/send-email.svg" alt="Measured on agentmods" height="20"></a>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.03206 |
| Opus 5 | $0.00019 | $0.01603 |
| Sonnet 5 | $0.00008 | $0.00641 |
| Haiku 4.5 | $0.00004 | $0.00321 |
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 yesterday.
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.
This is a copy
100% identical to send-email — 0 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.
How it starts
The opening of the file, as written. The whole thing — 133 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-shaperevise:<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 disclosure-emailer (vuln-scanner Arm C) — 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.mdwith the revised draft. Do NOT run the Send step. Arevise: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-emailheading inmemory/logs/${today}.md, then end the run.
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.
- yesterday First seen · 133 lines · 39 tokens per session scan A 67d4c34d7fcd
send-email is a skill published in the GitHub repository aaronjmars/aeon-agent (11 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 3,206 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to send-email, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
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…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
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.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.