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 skills add marian-kamenistak/claude-email-assistant --skill reply-emailgit clone --depth 1 https://github.com/marian-kamenistak/claude-email-assistantWrote 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/marian-kamenistak/claude-email-assistant/reply-email)<a href="https://agentmods.dev/skills/marian-kamenistak/claude-email-assistant/reply-email"><img src="https://agentmods.dev/badge/skills/marian-kamenistak/claude-email-assistant/reply-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.
<a href="https://agentmods.dev/skills/marian-kamenistak/claude-email-assistant/reply-email"><img src="https://agentmods.dev/badge/skills/marian-kamenistak/claude-email-assistant/reply-email.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.01264 |
| Opus 5 | $0.00015 | $0.00632 |
| Sonnet 5 | $0.00006 | $0.00253 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
reply-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 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.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Reply Skill
Draft email replies that sound like the user, not like AI.
Modes
Single reply (default)
/reply-email [message-id] or /reply-email + paste email text
Quick-reply shortcuts
/reply-email confirm [message-id]— 1-line confirmation/reply-email schedule [message-id]— propose dates + calendar link/reply-email followup [message-id]— gentle follow-up
Batch mode
When user says "draft all" or during morning triage:
- List all emails needing reply
- Draft all replies without asking
- Save all as Gmail Drafts
- Show summary with time estimates
Step 1: Get the email
# Fetch the full message
gws gmail users messages get --params '{"userId":"me","id":"MESSAGE_ID","format":"full"}' --format json
Step 2: Load voice context
Read these files before drafting (every time):
skills/reply-email/email-voice-guide.md— real examples of how you writeskills/reply-email/learned-replies.md— corrections from past sessionsshared/communication-style.md— writing rules
Step 3: Draft the reply
Rules
- Open with the person's name (first name)
- Get to the point in 1-2 sentences
- Keep it short — if it can be 3 lines, make it 3 lines
- Include calendar link when suggesting meetings
- No pleasantries ("Hope this finds you well")
- No corporate phrases ("Feel free to", "Don't hesitate to")
- No AI words (leverage, navigate, unlock, empower, delve, foster, robust, holistic)
- Always append the email signature (see below)
Email Signature (mandatory on every email)
Every email draft MUST include the signature from skills/reply-email/signature.html.
The signature has two parts:
- Profile photo + text block — Marian's headshot (round, 80px) next to name, title, contact info, and social links
- ELC Conference 26 banner — clickable banner image below the text block
CDN-hosted images (always use these URLs):
- Profile photo:
https://elc-decks.pages.dev/assets/img/marian-signature.png - ELC 26 banner:
https://elc-decks.pages.dev/assets/img/elc26-signature-banner.png
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 153 lines · 30 tokens per session scan A fb7c5eb7fe03
reply-email is a skill published in the GitHub repository marian-kamenistak/claude-email-assistant (2 stars, last pushed 17d ago), licensed MIT. It adds 30 tokens to every session and 1,264 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Originally from Garry Tan's gstack…
master
Turn reference docs into active mastery through retrieval practice, case binding, and scenario simulation. Combines Skycak (learning science) and Chin (expertise acceleration) frameworks. Use when you want to deeply learn material, not just read it.
upskilling-coach
Expert coach for learning, mastering, and upskilling in any domain. Use when the user wants to learn, master, improve, upskill, get better at, or get coached on any topic. Helps build consistent practice habits, identify prerequisites, design efficient learning loops, avoid common pitfalls, maintain discipline, and…
agentic-review
Deep multi-agent code review for local changes. Inspired by AmpCode's agentic review. Use when you want comprehensive analysis of staged changes, unstaged changes, specific commits, or branch differences. Spawns parallel specialized agents (security, performance, patterns, architecture) and synthesizes actionable…
qa
Full QA on all session changes using Codex as a second pair of eyes. Use when user says "QA", "full QA", "QA my changes", "QA all your changes", or "use codex to review". Runs git diff, sends changes to Codex for thorough review, and synthesizes findings.
design-swarm
Orchestrate a team of 10 design agents for holistic UI audit, ideation, and implementation. Use when: "design swarm", "holistic audit", "design review with all lenses", "full design analysis". Modes: audit, ideate, implement (any combination). Targets: screenshots, URLs, file paths, or text briefs.