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 commands/derek-larson14/delegate/mailgit clone --depth 1 https://github.com/derek-larson14/delegateWhat 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.00022 | $0.01575 |
| Opus 5 | $0.00011 | $0.00788 |
| Sonnet 5 | $0.00004 | $0.00315 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
mail scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL https://raw.githubusercontent.com/derek-larson14/delegate/main/ops/scripts/mail-cli.sh -o ./ops/scripts/mail-cli.sh 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.
Mac Mail Assistant
Access email via Mac Mail app using AppleScript. Works with ANY email provider configured in Mail.app (iCloud, Gmail, self-hosted IMAP, Exchange, etc).
Mac only. If the user is on Windows or Linux, tell them: "/mail uses Mac-only AppleScript. For email access, try Rube which can connect to Gmail, Outlook, and other email services."
Setup (check in order)
Step 1: Check if already working
./ops/scripts/mail-cli.sh status 2>&1
- If shows
MAIL_CONNECTEDwith accounts → ready. If user just said "/mail" with no specific request, ask: "What email task can I help with?" - If shows
MAIL_NOT_ACCESSIBLE→ need permission (Step 2) - If script not found → download it (Step 3)
Step 2: Grant Automation permission
Tell the user: "I need permission to access Mail.app."
Go to System Settings → Privacy & Security → Automation and enable:
- Obsidian (or Terminal) to control Mail
macOS will also prompt on first use - click Allow.
Step 3: Get the script (if missing)
mkdir -p ./ops/scripts
curl -sL https://raw.githubusercontent.com/derek-larson14/delegate/main/ops/scripts/mail-cli.sh -o ./ops/scripts/mail-cli.sh
chmod +x ./ops/scripts/mail-cli.sh
Commands
List recent emails:
./ops/scripts/mail-cli.sh list # 10 most recent
./ops/scripts/mail-cli.sh list 25 # 25 most recent
Read a specific email:
./ops/scripts/mail-cli.sh read <message_id>
Search emails (searches subject and sender):
./ops/scripts/mail-cli.sh search "meeting"
./ops/scripts/mail-cli.sh search "[email protected]"
Search by sender:
./ops/scripts/mail-cli.sh from "sarah"
Full-text search (includes body - slower):
./ops/scripts/mail-cli.sh search-body "project deadline"
List unread emails:
./ops/scripts/mail-cli.sh unread
./ops/scripts/mail-cli.sh unread 20 # limit to 20
List folders/mailboxes:
./ops/scripts/mail-cli.sh folders
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.
- 2d ago First seen · 228 lines · 22 tokens per session scan A 57abf981384b
mail is a command published in the GitHub repository derek-larson14/delegate (39 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 1,575 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.