triage

triage is a command for Claude Code from jonny-1812/corebee-mcp-skills. It costs 29 tokens per session (374 once invoked), scanned A, original, MIT.

A support-inbox review command that lists urgent, inactive, and active conversations, then suggests who could handle them.

In plain words
What is it for?
Use it to review open support conversations, identify overdue replies, inspect high-priority messages, and decide whether to assign or respond.
Why use it?
It helps you quickly find tickets needing attention without reading the entire queue. Assignments still require your approval.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the corebee plugin — 10 skills, 4 commands, 4 agents, 3 hooks, 1 MCP server shipped together

Good fit Use it to review open support conversations, identify overdue replies, inspect high-priority messages, and decide whether to assign or respond.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/jonny-1812/corebee-mcp-skills/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.

Clone the repo
git clone --depth 1 https://github.com/jonny-1812/corebee-mcp-skills

Made for: Claude Code.

Or install corebee, the plugin that ships this one along with the rest of its 10 skills, 4 commands, 4 agents, 3 hooks, 1 MCP server.

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 triage

README.md
[![agentmods](https://agentmods.dev/badge/commands/jonny-1812/corebee-mcp-skills/triage/github.svg)](https://agentmods.dev/commands/jonny-1812/corebee-mcp-skills/triage)
Your own site
<a href="https://agentmods.dev/commands/jonny-1812/corebee-mcp-skills/triage"><img src="https://agentmods.dev/badge/commands/jonny-1812/corebee-mcp-skills/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 triage

Your own site · 80×15
<a href="https://agentmods.dev/commands/jonny-1812/corebee-mcp-skills/triage"><img src="https://agentmods.dev/badge/commands/jonny-1812/corebee-mcp-skills/triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 374 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.00029 $0.00374
Opus 5 $0.00015 $0.00187
Sonnet 5 $0.00006 $0.00075
Haiku 4.5 $0.00003 $0.00037

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

Security

Grade A, and why

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.

commands/triage.md · 43 lines

What it actually says

/corebee:triage — Inbox Triage

Quickly review and prioritize the support queue.

Steps

  1. Call list_conversations with status: "open" to get all open conversations
  2. Call list_team_members to check who is available
  3. For each unassigned or high-priority conversation, call get_conversation to read the latest messages

Classify each conversation

  • Urgent: Unassigned AND (high priority OR no response for 4+ hours)
  • Needs response: Assigned but no activity for 4+ hours
  • In progress: Assigned and recently active

Output

Present as a prioritized list:

Urgent — Needs Immediate Attention

  • [Contact Name] — [Subject] — unassigned, [time] since last message → Suggest: Assign to [available agent] or respond now

Stale — Awaiting Response

  • [Contact Name] — [Subject] — assigned to [agent], [time] idle

Active — Being Handled

  • [Contact Name] — [Subject] — [agent] working, last activity [time ago]

Rules

  • Show names and emails, never raw UUIDs
  • Format times as "2 hours ago", "yesterday", etc.
  • If the user says "assign it", use assign_conversation
  • Never auto-assign without the user's explicit approval
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. 11d ago First seen · 43 lines · 29 tokens per session scan A 77c2e0e77f95

Subscribe to this mod's changes

triage is a command published in the GitHub repository jonny-1812/corebee-mcp-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 374 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.