What is inbound-triage?

A workflow that turns pasted messages, email threads, pull-request comments, meeting notes, or inbox files into grouped items ready for decisions. It removes duplicates and gives each item a numbered recommendation.

Use it to sort incoming feedback, identify duplicate or uncertain reports, and prepare selected issues for later action.

It prevents raw feedback from becoming an untracked list of vague requests. Nothing is sent for implementation or reply until an operator explicitly selects the items.

inbound-triage — Skill for Claude Code and Codex by EZotoff

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 EZotoff/ez-omo-config --skill inbound-triage

Clone the repo

git clone --depth 1 https://github.com/EZotoff/ez-omo-config

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ezotoff/ez-omo-config/inbound-triage/github.svg)](https://agentmods.dev/skills/ezotoff/ez-omo-config/inbound-triage)

Your own site

<a href="https://agentmods.dev/skills/ezotoff/ez-omo-config/inbound-triage"><img src="https://agentmods.dev/badge/skills/ezotoff/ez-omo-config/inbound-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/ezotoff/ez-omo-config/inbound-triage"><img src="https://agentmods.dev/badge/skills/ezotoff/ez-omo-config/inbound-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 982 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.00069	$0.00982
Opus 5	$0.00034	$0.00491
Sonnet 5	$0.00014	$0.00196
Haiku 4.5	$0.00007	$0.00098

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

Security

Grade A, and why

inbound-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 4d 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/inbound-triage/SKILL.md · 59 lines

How it starts

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

Inbound triage — raw input to decision-ready items

Triggers: a raw feedback/transcript paste ("Here are today's messages from Veran chat:", "Some feedback from Mauro:", "comments from the PR"), /triage, "triage this", "process the feedback", "triage the inbox"

The acceptance boundary (non-negotiable)

Nothing dispatches without selection. No implementation threads, backlog writes, replies, or session spawns until the operator picks numbered items.
Uncertain dedup is surfaced, never silenced. A "probably seen already" item is shown with its uncertainty, not auto-marked processed.

Input sources (in priority order)

Direct paste (primary) — raw text in the conversation, any channel, any format. This is the operator's real habit; NEVER redirect them to files. Record source as a short label like paste:mauro-chat-2026-08-28.
Inbox files (optional, for automation later) — <project>/.omo/inbox/*.md. Process unclaimed files (a file is consumed when a registry entry cites its name + content hash). A scheduled worker may use this dir eventually; the human never has to touch it.

Registry: <project>/.omo/inbox/registry.jsonl — one JSON object per item ever triaged, regardless of input source. The registry is the dedup memory; it is written by you at the selection checkpoint, not by the operator.

Workflow

1. Collect

Take the raw input from the paste above (or one inbox file at a time). If the paste is ambiguous about channel or sender, ask one clarifying question — otherwise proceed.

2. Parse to items

Split the dump into atomic items. Each item gets: id, source (file + channel), type (bug|request|concern|idea|decision), quote (verbatim, ≤200 chars), category, priority (P0–P3), feature attribution, context pointers. Items that are pure noise (greetings, logistics) are marked skipped with a one-line reason — never silently dropped.

Read the full file on GitHub · 59 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.

4d ago First seen · 59 lines · 69 tokens per session scan A ecfde2639a4c

Subscribe to this mod's changes

inbound-triage is a skill published in the GitHub repository EZotoff/ez-omo-config (6 stars, last pushed 5d ago), licensed MIT. It adds 69 tokens to every session and 982 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-09-06.

Planning Project management ai-coding coding-assistant developer-productivity oh-my-opencode opencode opencode-config

omc-plan

Strategic planning with optional interview workflow.

Yeachan-Heo/oh-my-claudecode · 11 tokens

launch

Shipyard's governed delivery pipeline — converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log. Two entry gates — the yard gate (drydock audit) and the fog gate (an effort…

Yeachan-Heo/oh-my-claudecode · 113 tokens

project-session-manager

Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.

Yeachan-Heo/oh-my-claudecode · 23 tokens

ask-navigator

Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding, not building: it…

Yeachan-Heo/oh-my-claudecode · 0 tokens

ultragoal

Durable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session.

Yeachan-Heo/oh-my-claudecode · 38 tokens

armada-gate

Run an evidence-gate checklist for each success criterion in the current phase. Use when checking if a phase is complete before marking it passed.

rafmacalaba/armada · 33 tokens