triage-labels

A reference table that assigns standard GitHub labels to issue-triage situations. Triage is the process of deciding what an issue needs and who should handle it.

In plain words
What is it for?
Use it when labeling GitHub issues as awaiting evaluation, awaiting reporter details, ready for an agent, ready for a human, or not planned for action.
Why use it?
It gives maintainers and contributors a shared vocabulary for whether an issue needs information, an agent, a person, or no action.

Agent

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.

agentmods
npx agentmods add agents/celados/mcpx/triage-labels
Clone the repo
git clone --depth 1 https://github.com/celados/mcpx
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 153 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00011 $0.00153
Opus 5 $0.00005 $0.00077
Sonnet 5 $0.00002 $0.00031
Haiku 4.5 $0.00001 $0.00015

Measured 3d ago against content hash 7a851e6ac67a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

triage-labels 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 3d 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.

docs/agents/triage-labels.md · 16 lines

What it actually says

Triage Labels

Role GitHub label Meaning
needs-triage needs-triage Maintainer evaluation required
needs-info needs-info Waiting for reporter information
ready-for-agent ready-for-agent Fully specified and agent-ready
ready-for-human ready-for-human Human implementation required
wontfix wontfix Will not be actioned
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. 3d ago First seen · 16 lines · 11 tokens per session scan A 7a851e6ac67a

Subscribe to this mod's changes

triage-labels is an agent published in the GitHub repository celados/mcpx (17 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 153 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.