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.
npx agentmods add agents/agentrhq/authsome/triage-labelsgit clone --depth 1 https://github.com/agentrhq/authsomeWhat 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 | $0.00000 | $0.00219 |
| Opus 5 | $0.00000 | $0.00110 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
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.
This is a copy
81% identical to triage — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 in this repo's 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 (e.g. "apply the AFK-ready triage label"), use the corresponding label string from this table.
Edit the right-hand column to match whatever vocabulary you actually use.
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.
- 2d ago First seen · 16 lines · 0 tokens per session scan A 4f53c9b40ce2
triage-labels is an agent published in the GitHub repository agentrhq/authsome (87 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 219 tokens. A static security scan graded it A with 0 findings. It is 81% identical to triage, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
issue-tracker
Issues for this repo live on the Open Software platform (os-platform), org june — NOT GitHub Issues. GitHub Issues exist on the repo but are a legacy/watchdog surface, not the triage queue.
product-manager
Use this agent for product development coordination, tracking tasks (GitHub Issues or local markdown), sprint planning, progress reporting, and development ceremony management. This PM does NOT use Jira.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and PRDs for this repo live as markdown files in a session-chosen working directory on the user's local machine. They are NOT tracked in git. The orchestrator (or the user) names a working root and tells the agent; the conventions below describe the file shape independent of where the root happens to be.
triage-labels
Five canonical triage roles map to this repo's label strings.
engineer
General-purpose software engineer. Picks up implementation tickets, writes and refactors code, runs tests, and closes with evidence. Good default for any ticket without a more specialized agent. Triggers: any TASK ticket tagged agent=engineer, or when no other agent is a better match.