inbox-triage

inbox-triage is a skill for Claude Code from Ootto-AI/claude-inbox-skills. It costs 67 tokens per session (548 once invoked), scanned A, original, MIT.

An inbox-sorting tool that places unread emails into reply now, later, or ignore categories and drafts responses for urgent messages.

In plain words
What is it for?
Use it to review unread emails, identify urgent requests, organize the rest, and prepare replies for messages that need an answer today.
Why use it?
It separates messages needing action from items that can wait or be archived, so a crowded inbox is easier to handle.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the claude-inbox-skills plugin — 5 skills shipped together

Good fit Use it to review unread emails, identify urgent requests, organize the rest, and prepare replies for messages that need an answer today.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ootto-ai/claude-inbox-skills/inbox-triage
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 Ootto-AI/claude-inbox-skills --skill inbox-triage
Clone the repo
git clone --depth 1 https://github.com/Ootto-AI/claude-inbox-skills

Made for: Claude Code.

Or install claude-inbox-skills, the plugin that ships this one along with the rest of its 5 skills.

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.

agentmods badge for inbox-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/ootto-ai/claude-inbox-skills/inbox-triage/github.svg)](https://agentmods.dev/skills/ootto-ai/claude-inbox-skills/inbox-triage)
Your own site
<a href="https://agentmods.dev/skills/ootto-ai/claude-inbox-skills/inbox-triage"><img src="https://agentmods.dev/badge/skills/ootto-ai/claude-inbox-skills/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.

agentmods 80×15 button for inbox-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/ootto-ai/claude-inbox-skills/inbox-triage"><img src="https://agentmods.dev/badge/skills/ootto-ai/claude-inbox-skills/inbox-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 548 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.00548
Opus 5 $0.00034 $0.00274
Sonnet 5 $0.00013 $0.00110
Haiku 4.5 $0.00007 $0.00055

Measured 12d ago against content hash dd4279f4d980, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 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.

skills/inbox-triage/SKILL.md · 51 lines

What it actually says

Inbox Triage

Sort a full inbox into reply-now / later / ignore, with drafts for the urgent ones.

When to use

Your inbox is full and you need to know what actually needs a response today, what can wait, and what to archive — plus ready-to-send drafts for the urgent ones.

What you'll need

A list of unread emails (sender, subject, and a line or two of each message — paste as many as you want).

Instructions

Collect any missing inputs from the user, then run this prompt:

You are my executive assistant triaging my inbox. Below is a list of unread emails, each with sender, subject, and a short preview.

[paste your emails here — one per block, with sender, subject, and preview]

Sort every email into exactly one of three buckets:
1. REPLY NOW — needs a response today (a real person waiting, a deadline, money, or a decision blocked on me)
2. LATER — matters but can wait this week (FYIs I should read, low-urgency requests)
3. IGNORE — newsletters, promos, automated notifications, or anything I can safely archive

For each email give one short line: sender — why it's in that bucket.
Then, for every REPLY NOW email only, write a ready-to-send draft reply: plain, friendly, professional, 2-4 sentences, no filler. If a reply needs information only I have, leave a clearly marked [blank] for me to fill.

Output as three headed sections (Reply Now, Later, Ignore), with the drafts under each Reply Now item.

Tip: Paste the actual preview text, not just subject lines — the more of each message Claude can see, the better it judges urgency and writes a usable draft.


Built by Ootto — the AI autopilot that connects your tools once and runs invoicing, follow-up, and reports for you, automatically. Book a demo →

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.

  1. 12d ago First seen · 51 lines · 67 tokens per session scan A dd4279f4d980

Subscribe to this mod's changes

inbox-triage is a skill published in the GitHub repository Ootto-AI/claude-inbox-skills (1 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 548 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.

Related

Other skills, from other repositories

domain

When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains / Afternic / Sedo / Dan), USPTO trademark screening, and social handle availability. Built on Laura Roeder's "work backwards from availability, not from a name you fell in love with"…

coreyhaines31/makerskills · 232 tokens

company-brain

Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…

coreyhaines31/makerskills · 322 tokens

slide-deck

When you want to draft, update, convert, or export a slide deck for a React/Next.js slide system (${SLIDEDECKREPO:-$HOME/code/your-slide-deck-site}/src/app/slides/). Writes TypeScript Slide[] arrays using your primitives (Eyebrow, Heading, Accent, Body, BulletList, Divider, TwoCol, GradientText), 12 cycling brand…

coreyhaines31/makerskills · 259 tokens

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…

cbrock84/headcount · 73 tokens

novu-design-workflow

Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state. Applies to BOTH dashboard-authored and code-first (@novu/framework) workflows. Use when planning a new workflow, deciding which channels to include…

novuhq/novu · 114 tokens

session-cleanup

Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation.…

hoangsonww/Claude-Code-Agent-Monitor · 67 tokens