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/foxzool/openlark/triage-labelsgit clone --depth 1 https://github.com/foxzool/openlarkWrote 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/foxzool/openlark/triage-labels)<a href="https://agentmods.dev/agents/foxzool/openlark/triage-labels"><img src="https://agentmods.dev/badge/agents/foxzool/openlark/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.00516 |
| Opus 5 | $0.00000 | $0.00258 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
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 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.
Category roles
The triage skill also speaks in terms of two category roles — bug (something is broken) and enhancement (new feature or improvement). Every triaged issue should carry exactly one category role and one state role.
This repo expresses category through its existing type: taxonomy rather than the canonical bug / enhancement names, keeping category orthogonal to the state machine above and consistent with the project's conventions:
| Canonical category | This repo's label | When to use |
|---|---|---|
bug |
bug |
缺陷修复（仓库已有 bug label） |
enhancement |
type:feat |
新功能或公开 API 增强（如补 accessor） |
enhancement |
type:refactor |
重构、清理、死码移除 |
enhancement |
type:docs / type:test / type:ci / type:policy |
文档 / 测试 / CI / 策略类改进 |
当 skill 提到 "apply a category role" 时，按上表选 type: 标签（bug 类用独立 bug label）。state 与 category 正交：一个 issue 同时带一个 state（最上面的表）+ 一个 category（本表）。
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 · 31 lines · 0 tokens per session scan A 39a9b40674ff
triage-labels is an agent published in the GitHub repository foxzool/openlark (105 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 516 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
debugger
Debugging specialist for errors and test failures. Use when encountering issues.
test-runner
Test automation expert. Use proactively to run tests and fix failures.
whiteboard-finish-reviewer
Reviews a finished Feishu whiteboard against its request, fact/design contract, rendered evidence, and medium rules, returning a bounded ship decision without editing files.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.