triage-labels

A reference table connecting five engineering triage roles to their GitHub issue labels. Triage means sorting incoming issues by what action or information they need.

In plain words
What is it for?
Use it when labeling GitHub Issues as needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix.
Why use it?
It keeps issue labels consistent when deciding whether an issue needs review, more details, 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/lexwdex/opencode-graphagent/triage-labels
Clone the repo
git clone --depth 1 https://github.com/LeXwDeX/OpenCode-GraphAgent
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 171 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.00000 $0.00171
Opus 5 $0.00000 $0.00086
Sonnet 5 $0.00000 $0.00034
Haiku 4.5 $0.00000 $0.00017

Measured 2d ago against content hash d13c0e8c4e4e, 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 2d 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 · 14 lines

What it actually says

Triage Labels

The engineering skills use five canonical triage roles. This table maps each role to the label used in this repository's GitHub Issues.

Canonical role GitHub label Meaning
needs-triage needs-triage A maintainer needs to evaluate the issue
needs-info needs-info Waiting for more information from the reporter
ready-for-agent ready-for-agent Fully specified and ready for an agent
ready-for-human ready-for-human Requires human implementation or judgment
wontfix wontfix Will not be actioned

When a skill mentions a triage role, use the corresponding GitHub label from this table.

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. 2d ago First seen · 14 lines · 0 tokens per session scan A d13c0e8c4e4e

Subscribe to this mod's changes

triage-labels is an agent published in the GitHub repository LeXwDeX/OpenCode-GraphAgent (111 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 171 tokens. 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.