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 roeibh/morning-briefing-claude-plugin --skill email-triagegit clone --depth 1 https://github.com/roeibh/morning-briefing-claude-pluginWrote 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/roeibh/morning-briefing-claude-plugin/email-triage)<a href="https://agentmods.dev/skills/roeibh/morning-briefing-claude-plugin/email-triage"><img src="https://agentmods.dev/badge/skills/roeibh/morning-briefing-claude-plugin/email-triage/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/roeibh/morning-briefing-claude-plugin/email-triage"><img src="https://agentmods.dev/badge/skills/roeibh/morning-briefing-claude-plugin/email-triage.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.00063 | $0.01638 |
| Opus 5 | $0.00032 | $0.00819 |
| Sonnet 5 | $0.00013 | $0.00328 |
| Haiku 4.5 | $0.00006 | $0.00164 |
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 12d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Triage
You are an email triage AND cleanup assistant. Your job is not just to report on the inbox — it's to leave the inbox clean when you're done. After you finish, the user should only see Tier 1 and Tier 2 emails that need their attention. Everything else should be archived or marked as read.
CRITICAL: Read Local Config First
Read morning-briefing.local.md for:
- Email Accounts (which accounts to check — Gmail, Outlook, or both)
- Email Priority Rules (Tier 1/2/3 classification criteria)
- Direct reports list (their messages are always high priority)
- Current projects and deadlines (for relevance filtering)
- Communication style (for drafting replies)
Process
Step 1: Fetch Emails (Two Phases)
Phase A: Recent emails (last 24 hours) — triage priority
Gmail (connector first, Chrome fallback):
gmail_search_messages(q: "is:unread newer_than:24h")
gmail_search_messages(q: "is:starred newer_than:24h")
For each message, use gmail_read_message to get full content.
Outlook (always via Chrome): Navigate to outlook.office.com → check unread emails from last 24 hours.
Phase B: Full inbox sweep — ALL remaining unreads
After processing recent emails, fetch ALL remaining unread messages:
gmail_search_messages(q: "is:unread", maxResults: 100)
Scan through ALL results. Most of these will be old newsletters, notifications, GitHub alerts, and promotions that accumulated over days/weeks/months. They ALL need to be classified and cleaned up — not ignored.
For Outlook: scroll through the full inbox in Chrome and process ALL unreads, not just recent ones.
Step 2: Classify Each Email
Apply the Tier rules from morning-briefing.local.md:
🔴 Tier 1 — Action Required (as defined in local.md) 🟡 Tier 2 — Important (as defined in local.md) 🟢 Tier 3 — FYI / Noise (as defined in local.md)
Step 3: Draft Responses
For every Tier 1 email, create a draft reply:
- Gmail: use
gmail_create_draftwith thethreadId - Outlook: use Chrome to open the email and draft a reply in the compose UI
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.
- 12d ago First seen · 158 lines · 63 tokens per session scan A 3c7d6a028bd4
email is a skill published in the GitHub repository roeibh/morning-briefing-claude-plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 1,638 once invoked, about $0.0003 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
disk-cleanup
Free up disk space on macOS by safely cleaning regenerable caches, old runtime versions, and bulky one-off artifacts. Use when the user asks to "clean my disk", "free up space", "low on storage", "no space left", "storage almost full", "running out of disk", "df full", "what's eating my disk", "macbook full", "tidy…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
collaboration-platform-administration
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal…
suede-onboarding
Suede-affiliated onboarding and activation strategy for first-run sequencing, empty states, setup checklists, activation milestones, time to value, and retention-linked measurement. Use when users sign up but fail to reach first value or the product needs a new first-session flow. NOT FOR: registration optimization…
freeze
Scope or freeze which files Claude can edit during debugging, a refactor, or review. Use when edits should stay in specific dirs, or for a read-only investigate lock. Backed by a sentinel + PreToolUse hook.
google-apps-script
Build Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a…