agentmods.dev

follow-up

follow-up is a skill for Claude Code from laschopin/better-email-mcp-worker. It costs 20 tokens per session (616 once invoked), scanned A, a copy of follow-up, MIT.

A workflow for finding emails that need a reply and drafting responses with their surrounding context. It checks sent mail against inbox replies and reviews flagged messages that have not been answered.

In plain words
What is it for?
Use it to find unanswered sent emails, check flagged unreplied messages, and prepare contextual follow-up drafts.
Why use it?
It helps find messages that may be forgotten after several days or marked for attention. Matching subjects and senders provides evidence that a reply has not already arrived.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the better-email-mcp plugin — 2 skills, 1 MCP server shipped together

not rated 0repo 1mo ago A scan 20 tokens copy · 88% MIT

Good fit Use it to find unanswered sent emails, check flagged unreplied messages, and prepare contextual follow-up drafts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/laschopin/better-email-mcp-worker/follow-up
View source ↗ laschopin/better-email-mcp-worker
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 laschopin/better-email-mcp-worker --skill follow-up
Clone the repo
git clone --depth 1 https://github.com/laschopin/better-email-mcp-worker

Made for: Claude Code.

Or install better-email-mcp, the plugin that ships this one along with the rest of its 2 skills, 1 MCP server.

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 follow-up

README.md
[![agentmods](https://agentmods.dev/badge/skills/laschopin/better-email-mcp-worker/follow-up/github.svg)](https://agentmods.dev/skills/laschopin/better-email-mcp-worker/follow-up)
Your own site
<a href="https://agentmods.dev/skills/laschopin/better-email-mcp-worker/follow-up"><img src="https://agentmods.dev/badge/skills/laschopin/better-email-mcp-worker/follow-up/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 follow-up

Your own site · 80×15
<a href="https://agentmods.dev/skills/laschopin/better-email-mcp-worker/follow-up"><img src="https://agentmods.dev/badge/skills/laschopin/better-email-mcp-worker/follow-up.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 616 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 88% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00616
Opus 5 $0.00010 $0.00308
Sonnet 5 $0.00004 $0.00123
Haiku 4.5 $0.00002 $0.00062

Measured 11d ago against content hash 520255f2fcb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

follow-up 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 11d 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

88% identical to follow-up — 6 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/follow-up/SKILL.md · 78 lines

How it starts

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

Follow-Up

Find emails that need follow-up and draft contextual responses.

Unanswered Sent Emails

Find emails you sent that received no reply after N days:

  1. Search Sent folder for emails sent N+ days ago:

    messages(action="search", query="SINCE 2026-03-16 BEFORE 2026-03-20", folder="Sent", account="...")

  2. Cross-reference Inbox for replies:

    • For each sent email, search Inbox for matching Subject (with Re: prefix): messages(action="search", query="SUBJECT \"Re: <original subject>\" FROM <recipient>")
    • If no matching reply found, this email needs follow-up

  3. Present candidates with context:

    No reply after 5 days:
1. "API Integration Proposal" to [email protected] (sent Mar 18)
   Original: Asked about timeline for API access
2. "Invoice #2024-003" to [email protected] (sent Mar 16)
   Original: Sent invoice, requested payment confirmation

Flagged but Unreplied

Find received emails you flagged/starred but never responded to:

messages(action="search", query="FLAGGED", account="...")

Then for each flagged email, check Sent folder for a reply with matching subject. If none found, it needs attention.

Drafting Follow-Up Messages

For each follow-up candidate:

  1. Read the original thread to get full context

  2. Decide reply type:

    • If original was your sent email with no reply: draft a gentle follow-up referencing the original
    • If original was received and you haven't replied: draft a response to their message

  3. Use reply (not new message) when following up on existing threads:

    send(action="reply", message_id="<original_msg_id>", body="<follow-up text>")

    Only use send(action="send") for new conversations.

  4. Follow-up tone guidelines:

    • First follow-up (3-5 days): "Just checking in on this..."
    • Second follow-up (7-10 days): "Wanted to circle back on..."
    • Final follow-up (14+ days): Direct ask with deadline: "Could you confirm by Friday?"

Read the full file on GitHub · 78 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. 11d ago First seen · 78 lines · 20 tokens per session scan A 520255f2fcb0

Subscribe to this mod's changes

follow-up is a skill published in the GitHub repository laschopin/better-email-mcp-worker (0 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 616 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to follow-up, differing in 6 lines, and is treated as a copy.

Productivity
Related

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…

nexu-io/open-design · 117 tokens

agentmail

Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.

paperclipai/paperclip · 30 tokens

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…

danielmiessler/LifeOS · 196 tokens

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.

pinchtab/pinchtab · 52 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

the-open-agent/openagent · 17 tokens