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/fuyuxiang/echo-agent/email-assistantnpx skills add fuyuxiang/echo-agent --skill email-assistantgit clone --depth 1 https://github.com/fuyuxiang/echo-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/fuyuxiang/echo-agent/email-assistant)<a href="https://agentmods.dev/skills/fuyuxiang/echo-agent/email-assistant"><img src="https://agentmods.dev/badge/skills/fuyuxiang/echo-agent/email-assistant.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 | $0.00029 | $0.00488 |
| Opus 5 | $0.00015 | $0.00244 |
| Sonnet 5 | $0.00006 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
email-assistant 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 5d 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.
What it actually says
Email Assistant
Two options: Himalaya CLI (modern, Rust-based) or Python imaplib fallback.
Option A: Himalaya (Recommended)
brew install himalaya # or cargo install himalaya
himalaya account configure
Read
himalaya envelope list
himalaya envelope list --folder INBOX --page-size 10
himalaya message read <id>
Search
himalaya envelope list --folder INBOX subject "weekly report"
himalaya envelope list from "[email protected]"
Send
himalaya message write
# Or via template:
himalaya template write | himalaya message send
Reply/Forward
himalaya message reply <id>
himalaya message forward <id>
Option B: Python Fallback
Environment variables:
export ECHO_EMAIL_HOST=imap.gmail.com
export [email protected]
export ECHO_EMAIL_PASS=app-password
export ECHO_SMTP_HOST=smtp.gmail.com
export ECHO_SMTP_PORT=587
python3 scripts/email_client.py list --host imap.example.com --user [email protected] --password xxx --count 10
python3 scripts/email_client.py search --host imap.example.com --user [email protected] --password xxx "urgent"
python3 scripts/email_client.py send --smtp-host smtp.example.com --user [email protected] --password xxx --to "[email protected]" --subject "Hi" --body "Content"
Common Workflows
- Morning email digest: fetch unread, summarize subjects
- Draft reply: compose response based on context
- Search by sender/date/subject
Security
- Store credentials in environment variables, never in chat
- Use app-specific passwords (Gmail requires this)
- Consider OAuth2 for production use
What ships with it
1 file 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.
- 5d ago First seen · 81 lines · 29 tokens per session scan A d9c090451d9f
email-assistant is a skill published in the GitHub repository fuyuxiang/echo-agent (988 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 488 once invoked, about $0.0001 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-30.
Other skills, from other repositories
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
bootstrap
Onboarding conversation to generate a user profile.
efficient-execution
Reduce token waste and task completion time by choosing the simplest tool for each job.
cron
Schedule reminders and recurring tasks.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes, capturing pane output, and managing terminal multiplexer windows. Enables parallel coding-agent orchestration, background process management, and REPL interaction via sockets. Use when the agent needs to launch, monitor, or coordinate…
local-tools
Access local system resources including Calendar on macOS and Windows. Use this skill when you need to manage user's schedule directly on their device.