Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yjwong/lark-clinpx agentmods add skills/yjwong/lark-cli/emailWrote 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/yjwong/lark-cli/email)<a href="https://agentmods.dev/skills/yjwong/lark-cli/email"><img src="https://agentmods.dev/badge/skills/yjwong/lark-cli/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/yjwong/lark-cli/email"><img src="https://agentmods.dev/badge/skills/yjwong/lark-cli/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.00029 | $0.01344 |
| Opus 5.5 | $0.00012 | $0.00538 |
| Sonnet 5.5 | $0.00006 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Management Skill
Read and search emails from Lark Mail via the lark CLI using IMAP with local caching.
Setup
Before using mail commands, IMAP credentials must be configured:
lark mail setup
This will prompt for IMAP credentials. See: https://www.larksuite.com/hc/en-US/articles/378111206512-log-in-to-lark-mail-through-a-third-party-email-client
Running Commands
Ensure lark is in your PATH, or use the full path to the binary. Set the config directory if not using the default:
lark mail <command>
# Or with explicit config:
LARK_CONFIG_DIR=/path/to/.lark lark mail <command>
Commands Reference
Check Status
lark mail status
Shows connection status and cache freshness. The freshness field indicates how stale the cached data is.
List Mailboxes
lark mail list
Sync Emails
Fetch new emails from the server into the local cache:
# Sync INBOX (default)
lark mail sync
# Sync with more parallel connections (faster for large mailboxes)
lark mail sync --workers 20
# Sync specific mailbox
lark mail sync --mailbox Sent
Flags:
--mailbox,-m: Mailbox to sync (default: INBOX)--workers,-w: Number of parallel connections (default: 10)
Important:
- Run sync before searching if you need fresh data
- Sync is resumable - if interrupted, running it again only fetches messages not already cached
Search Emails
Search the local cache (fast, no network calls):
# List recent emails
lark mail search
# Filter by sender
lark mail search --from [email protected]
# Filter by subject
lark mail search --subject "Q4 Report"
# Filter by date range
lark mail search --since 2025-01-01 --before 2025-01-15
# Combined filters
lark mail search --from [email protected] --since 2025-01-01 --limit 10
# Search different mailbox
lark mail search --mailbox Sent
View Email Content
lark mail show --uid <uid>
The UID is obtained from search results.
Download as .eml
lark mail fetch --uid <uid>
lark mail fetch --uid <uid> --output ./emails/
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 · 228 lines · 29 tokens per session scan A 1df026e6fa07
email is a skill published in the GitHub repository yjwong/lark-cli (54 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 1,344 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.
Other skills, from other repositories
lark-meeting
Use Lark CLI to locate meetings, manage Minutes and AI notes, inspect transcripts, and run authorized live-meeting interactions.
slackcli
Read, send, search, and manage Slack workspaces with the slackcli binary. Installs slackcli if missing and checks or proposes authentication first. Use whenever the user mentions Slack or pastes a slack.com link.
tokf-discover
Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.