A procedure for replying to an email while preserving the full conversation context. It finds the message, loads its thread, identifies the mailbox, and displays the history in order.

Use it when continuing a specific email conversation and you need the prior messages, recipients, and mailbox identity before drafting a reply.

It reduces the chance of replying without seeing earlier messages or sending the response to the wrong recipients.

email-reply — Skill for Claude Code by inboxapi/cli

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 inboxapi/cli --skill email-reply

Clone the repo

git clone --depth 1 https://github.com/inboxapi/cli

Made for: Claude Code.

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/inboxapi/cli/email-reply/github.svg)](https://agentmods.dev/skills/inboxapi/cli/email-reply)

Your own site

<a href="https://agentmods.dev/skills/inboxapi/cli/email-reply"><img src="https://agentmods.dev/badge/skills/inboxapi/cli/email-reply/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/inboxapi/cli/email-reply"><img src="https://agentmods.dev/badge/skills/inboxapi/cli/email-reply.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,272 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.

Model	Per session	Once invoked
Fable 5.1	$0.00030	$0.01272
Opus 5.5	$0.00012	$0.00509
Sonnet 5.5	$0.00006	$0.00254
Haiku 4.5	$0.00003	$0.00127

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

Security

Grade A, and why

email-reply 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.

skills/claude/email-reply/SKILL.md · 105 lines

How it starts

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

Email Reply

Help the user reply to an email with full thread context.

Steps

Find the email:
- Try npx -y @inboxapi/cli get-email "$ARGUMENTS" first — if it succeeds, use that email
- If it fails (e.g., not a valid message ID), fall back to npx -y @inboxapi/cli search-emails --subject "<query>" with the argument as subject/keyword
- If multiple results, present them and ask the user to pick one
Load thread context: Run: npx -y @inboxapi/cli get-thread --message-id "<message-id>" with the email's message ID to show the full conversation
Load mailbox identity: Run npx -y @inboxapi/cli whoami so you know the current mailbox email and can exclude only that mailbox from preserved thread recipients

Display thread: Show the conversation history in chronological order:

--- Thread: <subject> ---

[1] From: [email protected]
    To: [email protected], [email protected]
    Cc: [email protected]
    Reply-To: [email protected]
    Date: Jan 15, 2:30 PM
    Subject: <subject>
> Original message text...

[2] From: [email protected]
    To: [email protected]
    Date: Jan 15, 3:00 PM
    Subject: Re: <subject>
> Your previous reply...

[3] From: [email protected]
    To: [email protected], [email protected]
    Cc: [email protected]
    Reply-To: [email protected]
    Date: Jan 15, 4:15 PM
    Subject: Re: <subject>
> Latest message you're replying to...

Compose reply: Ask the user what they want to say in their reply
Preview: Show the reply before sending:
```
Replying to: [email protected]
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: <subject>
---
<reply body>
```
Preview the likely To/Cc set using the thread context:
- primary To is Reply-To if present, otherwise the original sender
- preserve all original thread participants from To/Cc in Cc
- exclude only the current mailbox itself
- use the mailbox email from whoami to determine which participant is “self”
- use --cc only for new recipients beyond the original thread Treat this as a preview heuristic. The authoritative final recipient set is whatever send-reply returns after the send.

Read the full file on GitHub · 105 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 · 105 lines · 30 tokens per session scan A 665b598e5b0c

Subscribe to this mod's changes

email-reply is a skill published in the GitHub repository inboxapi/cli (13 stars, last pushed 24d ago), licensed MIT. It adds 30 tokens to every session and 1,272 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.

Writing and docs ai ai-agent email email-sender mcp mcp-client

anonsec-mcp-server

Firefox Relay MCP Server (anonsec-mcp-server) is a production-grade Model Context Protocol server that provides comprehensive anonymous email management capabilities through Firefox Relay addresses. Built with privacy, security, and operational excellence as core principles, this server enables AI agents and…

VRIL-LABS/anonsec-mcp-server · 0 tokens

code_explorer

Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.

google-gemini/gemini-cli · 28 tokens

quality

Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

google-gemini/gemini-cli · 24 tokens

amazon aurora dsql

Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.

awslabs/mcp · 46 tokens

session-investigator

Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…

evalstate/fast-agent · 68 tokens

decocms-ui

Build or style React UI with the decocms product design system (@decocms/ui). Use when creating interfaces, pages, or components in a project that should look like decocms products, when the user mentions "design system", "@decocms/ui", "decocms style", or asks to make UI consistent with Studio. Covers installation…

decocms/studio · 91 tokens