What is daily-inbox-triage?

A morning review of unread email, Slack messages, and Telegram direct messages. It sorts them by urgency and creates a short action list with draft replies for items that need a response.

It is for collecting unread messages, identifying who wants what, prioritizing items, and drafting replies to urgent requests or decisions.

It turns several message streams into one focused report, helping you separate urgent work and decisions from information, noise, and spam.

daily-inbox-triage — Skill for Claude Code by OnlyTerp

Install

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.

Any agent

npx skills add OnlyTerp/hermes-optimization-guide --skill daily-inbox-triage

Clone the repo

git clone --depth 1 https://github.com/OnlyTerp/hermes-optimization-guide

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/onlyterp/hermes-optimization-guide/daily-inbox-triage/github.svg)](https://agentmods.dev/skills/onlyterp/hermes-optimization-guide/daily-inbox-triage)

Your own site

<a href="https://agentmods.dev/skills/onlyterp/hermes-optimization-guide/daily-inbox-triage"><img src="https://agentmods.dev/badge/skills/onlyterp/hermes-optimization-guide/daily-inbox-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/onlyterp/hermes-optimization-guide/daily-inbox-triage"><img src="https://agentmods.dev/badge/skills/onlyterp/hermes-optimization-guide/daily-inbox-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,064 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00027	$0.01064
Opus 5	$0.00014	$0.00532
Sonnet 5	$0.00005	$0.00213
Haiku 4.5	$0.00003	$0.00106

Measured 10d ago against content hash 841c83943312, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

daily-inbox-triage 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 10d 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.

skills/ops/daily-inbox-triage/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

daily-inbox-triage — Morning Sweep

Produce a one-screen triage report: what's urgent, what's a decision, what's noise, with a draft reply per actionable item.

Procedure

Collect unread items from each configured channel within window:. Cap at 200 items; if over, prioritize starred / mentions / VIP-list senders.
Classify every item into one of:
- urgent — time-sensitive, needs action today
- decision — needs a yes/no/pick from me
- info — FYI; noting what they said is enough
- noise — newsletters, generic updates, obvious marketing
- spam — confident spam (see spam-trap)
Summarize per item: one line of "who / what / ask". Keep under 80 chars.
Draft replies for every urgent and decision item. Keep replies under 4 sentences. Never include URLs the sender supplied without sanitizing.

Output as a single markdown message:

## Inbox Triage — {date}, last {window}

### Urgent ({n})
- [email] Alice @ Acme — blocker on staging auth → draft: "{reply}" [/approve 1]
- [slack] #incidents — payment API 500s → draft: "{reply}" [/approve 2]

### Decisions ({n})
- [telegram] @pm — approve Q3 roadmap doc? → draft: "{reply}" [/approve 3]

### FYI ({n})
- {brief one-liners}

### Noise ({n})
- {unsubscribable patterns suggested}

Surface:
- Any item matching a VIP sender pattern (from config) gets escalated regardless of classifier.
- Any item mentioning "urgent", "asap", "incident", "outage", "production" escalates to urgent even if classifier disagreed.
Never:
- Send replies automatically. Approval is required for every outbound.
- Follow links from untrusted senders.
- Summarize attachments without explicit user consent (privacy + prompt-injection risk).

Example config snippet

There is no skills.overrides: block in config.yaml — per-skill settings (like the VIP-sender list) are declared in the skill's OWN frontmatter via metadata.hermes.config (see user-guide/features/skills.md), or just hardcoded in the skill file:

Read the full file on GitHub · 111 lines

Changes

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.

10d ago First seen · 111 lines · 27 tokens per session scan A 841c83943312

Subscribe to this mod's changes

daily-inbox-triage is a skill published in the GitHub repository OnlyTerp/hermes-optimization-guide (640 stars, last pushed 13d ago), licensed MIT. It adds 27 tokens to every session and 1,064 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.

Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

daily-inbox-triage