inbox-meeting-triage

inbox-meeting-triage is a skill for Claude Code, Codex from ntaffzii/Skill-Agents. It costs 71 tokens per session (290 once invoked), scanned A, original, MIT.

A workflow for sorting email, chat messages, calendar events, and meeting information into clear actions. It can prepare notes, draft replies, and outline possible tasks or issues.

In plain words
What is it for?
Use it to prepare for meetings, plan the day, find follow-ups, draft email or chat responses, and turn messages into issue or task drafts. It can also format useful notes for a personal knowledge system.
Why use it?
It turns scattered communication into a manageable list of decisions and follow-ups. It also keeps drafts separate so replies and tasks are not sent or created automatically.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare for meetings, plan the day, find follow-ups, draft email or chat responses, and turn messages into issue or task drafts. It can also format useful notes for a personal knowledge system.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ntaffzii/skill-agents/inbox-meeting-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 ntaffzii/Skill-Agents --skill inbox-meeting-triage
Clone the repo
git clone --depth 1 https://github.com/ntaffzii/Skill-Agents

Made for: Claude Code, Codex.

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-meeting-triage

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/ntaffzii/skill-agents/inbox-meeting-triage"><img src="https://agentmods.dev/badge/skills/ntaffzii/skill-agents/inbox-meeting-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 290 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.00071 $0.00290
Opus 5 $0.00036 $0.00145
Sonnet 5 $0.00014 $0.00058
Haiku 4.5 $0.00007 $0.00029

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

Security

Grade A, and why

inbox-meeting-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/productivity/inbox-meeting-triage/SKILL.md · 50 lines

What it actually says

Inbox Meeting Triage

Use this skill to turn communication noise into a small set of decisions and actions.

Workflow

  1. Gather supplied or configured sources.

    • Calendar events for time commitments.
    • Email messages for inbox actions.
    • Slack/Discord messages for chat actions.
    • Notion/Obsidian/memory for context.
  2. Classify each item.

    • Reply
    • Schedule
    • Decide
    • Delegate
    • Read later
    • Turn into issue/task
    • Archive/no action
  3. Draft outputs.

    • Meeting prep note.
    • Email/chat replies.
    • Issue/task drafts.
    • Obsidian-ready daily note section.
  4. Verify privacy.

    • Do not send replies automatically.
    • Do not create issues automatically.
    • Do not expose private message content in public-facing summaries.

Output Shape

Use compact sections:

  • Calendar
  • Inbox
  • Chat
  • Actions
  • Draft Replies
  • Issues/Tasks
  • Notes To Save
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 · 50 lines · 71 tokens per session scan A cc416bd5b4e7

Subscribe to this mod's changes

inbox-meeting-triage is a skill published in the GitHub repository ntaffzii/Skill-Agents (4 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 290 once invoked, about $0.0004 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.