What is inbox-triage?

A workflow for sorting unread email and Slack messages into priority groups and suggesting next actions.

Use it to find urgent requests, draft reply suggestions, identify meeting-related messages, and offer to archive low-value automated mail.

It reduces the effort of reviewing a crowded inbox and separates messages that need replies from notifications or information-only updates.

inbox-triage — Skill for Claude Code by kenshikobayashi

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 kenshikobayashi/everything-claude-code-for-business --skill inbox-triage

Clone the repo

git clone --depth 1 https://github.com/kenshikobayashi/everything-claude-code-for-business

Made for: Claude Code.

Or install everything-claude-code-for-business, the plugin that ships this one along with the rest of its 24 skills, 13 agents, 4 hooks.

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/kenshikobayashi/everything-claude-code-for-business/inbox-triage/github.svg)](https://agentmods.dev/skills/kenshikobayashi/everything-claude-code-for-business/inbox-triage)

Your own site

<a href="https://agentmods.dev/skills/kenshikobayashi/everything-claude-code-for-business/inbox-triage"><img src="https://agentmods.dev/badge/skills/kenshikobayashi/everything-claude-code-for-business/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/kenshikobayashi/everything-claude-code-for-business/inbox-triage"><img src="https://agentmods.dev/badge/skills/kenshikobayashi/everything-claude-code-for-business/inbox-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 510 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.

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.00014	$0.00510
Opus 5	$0.00007	$0.00255
Sonnet 5	$0.00003	$0.00102
Haiku 4.5	$0.00001	$0.00051

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

Security

Grade A, and why

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 11d 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/inbox-triage/SKILL.md · 63 lines

What it actually says

You are executing the /inbox-triage command. Perform bulk triage of the user's unread messages.

Arguments

$ARGUMENTS may contain: --email-only, --slack-only, --since "Xh ago"

Steps

Fetch: Pull unread messages from Gmail and Slack in parallel (or one only if flag set)
Classify each message into 4 tiers:
- Skip: Bot notifications, automated alerts, marketing → recommend auto-archive
- Info Only: CC'd emails, announcements, FYI messages → no action needed
- Meeting Info: Calendar invites, scheduling, agenda → calendar-related action
- Action Required: Direct asks, deadlines, approvals → needs response
Prioritize Action Required items by:
- Sender importance (from CLAUDE.md team context)
- Deadline proximity
- Explicit urgency signals
Suggest actions for top items:
- Draft reply suggestions for Action Required items
- Offer to bulk-archive Skip items

Output Format

## Inbox Triage — [Date] [Time]

### Action Required ([N] items) — sorted by priority
| # | Source | From | Subject/Topic | Urgency | Suggested Action |
|---|--------|------|---------------|---------|-----------------|
| 1 | Gmail | CFO | Budget approval | ★★★ | Reply with figures |
| 2 | Slack | @alice (#eng) | PR review | ★★ | Review PR #234 |

### Meeting Info ([N] items)
- [Invite]: Q1 Planning — Accept? [yes/no/tentative]

### Info Only ([N] items)
- [Summary of informational messages]

### Skip ([N] items) — recommend archive
- [N] bot notifications, [N] marketing emails
→ Archive all? [confirm]

### Quick Actions
Would you like me to:
- [ ] Draft replies for Action Required items?
- [ ] Archive Skip items?
- [ ] Create tasks for Action Required items?

Constraints

Never auto-archive without user confirmation
Show enough context to make a quick decision (sender, subject, first line)
If Gmail/Slack is not connected, note it and skip that source

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.

11d ago First seen · 63 lines · 14 tokens per session scan A 18d6271299d8

Subscribe to this mod's changes

inbox-triage is a skill published in the GitHub repository kenshikobayashi/everything-claude-code-for-business (2 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 510 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-31.

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

inbox-triage