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/clay-good/openlore/triage-labelsgit clone --depth 1 https://github.com/clay-good/OpenLoreWrote 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.
[](https://agentmods.dev/agents/clay-good/openlore/triage-labels)<a href="https://agentmods.dev/agents/clay-good/openlore/triage-labels"><img src="https://agentmods.dev/badge/agents/clay-good/openlore/triage-labels.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00400 |
| Opus 5 | $0.00000 | $0.00200 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 4d 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.
What it actually says
Triage Labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the label strings that actually exist in this repo's issue tracker.
This repo uses the stock GitHub label set — no new labels are created for triage.
| Canonical role | Label in our tracker | Meaning |
|---|---|---|
needs-triage |
(none — see below) | Maintainer needs to evaluate this issue |
needs-info |
question |
Waiting on reporter for more information |
ready-for-agent |
(none — see below) | Fully specified, ready for an AFK agent |
ready-for-human |
help wanted |
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.
The two roles with no label
needs-triage and ready-for-agent have no equivalent in the stock set. Do not
substitute a close-enough label (bug, enhancement, and good first issue mean other
things, and mislabelling is worse than not labelling). Instead, state the state
explicitly in a comment on the issue, so it stays visible and greppable:
gh issue comment <number> --body "Triage state: ready-for-agent — fully specified, no human context required."
A triage pass that lands on one of these two roles is complete only once that comment exists. Never silently drop the state.
Changing this
If those two roles get real labels later, create them and replace the (none) cells — nothing else needs to change.
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.
- 4d ago First seen · 37 lines · 0 tokens per session scan A 5aeffa050776
triage-labels is an agent published in the GitHub repository clay-good/OpenLore (292 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 400 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.
Other agents, from other repositories
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
sweep-scan
You are a backlog sweeper. ./input.json names one repo and the exact source tree to read it against.
progress
$frontend-delivery NEW/REPLAN -> Brain analysis + stack discovery -> close Brain -> one Orchestrator child (intent=deliver) -> controller-action loop -> jira-call -> Primary Controller -> confirmed result -> same Orchestrator -> dispatch-specialist -> Primary Controller -> specialist -> cleanup/close -> result -> same…
context-auditor
Audits .context/ project content (references, docs, plans, issues, roadmap, requests, decisions, audits) for structural compliance.
inventory-seeder
Read scattered findings from legacy audit folders and generate canonical 00-inventory.md rows. Used by /aidex-audit migrate after folders have been moved.
CLAUDE
Provides specialized subagents for complex operations in team-management, including multi-provider issue tracking synchronization (GitLab, Jira, GitHub / Gitea), code review, and task management automation.