triage-labels

A lookup table that connects standard issue-triage roles to the label names used in a GitHub issue tracker. Triage means reviewing an issue and deciding what should happen next.

In plain words
What is it for?
Use it when assigning or interpreting the labels needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix.
Why use it?
It prevents skills from applying the wrong label when they refer to roles such as needing more information or being ready for an agent.

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/spiritledsoftware/caplets/triage-labels
Clone the repo
git clone --depth 1 https://github.com/spiritledsoftware/caplets
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 211 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.00211
Opus 5 $0.00000 $0.00105
Sonnet 5 $0.00000 $0.00042
Haiku 4.5 $0.00000 $0.00021

Measured yesterday against content hash 958d3c05da01, 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 yesterday.

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

The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used for this repo's GitHub issue tracker.

Label in mattpocock/skills Label in our tracker Meaning
needs-triage needs-triage Maintainer needs to evaluate this issue
needs-info needs-info Waiting on reporter for more information
ready-for-agent ready-for-agent Fully specified, ready for an AFK agent
ready-for-human ready-for-human Requires human implementation
wontfix wontfix Will not be actioned

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

Edit the right-hand column if the repo later adopts different GitHub label names.

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. yesterday First seen · 16 lines · 0 tokens per session scan A 958d3c05da01

Subscribe to this mod's changes

triage-labels is an agent published in the GitHub repository spiritledsoftware/caplets (14 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 211 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.