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/gvastethecreator/codex-studio/triage-labelsgit clone --depth 1 https://github.com/gvastethecreator/codex-studioWrote 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/gvastethecreator/codex-studio/triage-labels)<a href="https://agentmods.dev/agents/gvastethecreator/codex-studio/triage-labels"><img src="https://agentmods.dev/badge/agents/gvastethecreator/codex-studio/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 fields
GitHub Issues use one category label and one triage label. Local mirrors record the same values.
Categories
| Canonical category | GitHub label | Meaning |
|---|---|---|
bug |
bug |
Existing behavior is wrong |
enhancement |
enhancement |
New behavior or improvement |
Statuses
| Canonical status | GitHub label | Meaning |
|---|---|---|
needs-triage |
needs-triage |
Maintainer evaluation required |
needs-info |
needs-info |
Waiting for missing information |
ready-for-agent |
ready-for-agent |
Fully specified and ready for an AFK agent |
ready-for-human |
ready-for-human |
Needs human implementation or judgment |
wontfix |
wontfix |
Deliberately not actioned |
Project status
Project 8 uses the Status field with these exact values:
| Workflow state | Project value |
|---|---|
| Queued | Todo |
| Active | In Progress |
| Finished | Done |
When triage changes, update the GitHub label and the local Category: or Status: field together. When work starts or finishes, update the Project item and the local Project status: field together.
Local Execution: is separate from triage Status:. Use queued, active, blocked, or finished.
Workflow labels
spec: parent specification for implementation ticketswayfinder:map: parent decision map
Create more workflow labels only when an enabled workflow needs them. Preserve existing repository vocabulary when it has the same meaning.
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 · 42 lines · 0 tokens per session scan A 98de06a21a34
triage-labels is an agent published in the GitHub repository gvastethecreator/codex-studio (12 stars, last pushed 5d ago), 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
triage-issues-and-prs
GitHub issue and PR triage agent for slopus/happy. Use when you need to: review open issues/PRs, find duplicates, identify what needs a reply, close resolved items, draft maintainer responses, or get a status overview of the backlog. Invoke with /triage or when asked about issues, PRs, contributors, or community…
issue-tracker
Issues and PRDs for this repo live as tasks on the dev-3.0 Kanban board, managed through the dev3 CLI (the same board this project ships). There is no separate issue tracker — a task is an issue. External GitHub PRs are pulled in as a secondary triage surface (see below).
triage-labels
All canonical role labels are configured in GitHub.
planner
Use proactively for everyday planning, requirement cleanup, and decomposing work into milestones, features, and tasks. For major product or architecture decisions, prefer architect.
brainstorm-audit-agent
You are an independent design reviewer. Review BRAINSTORM.md to find issues that main agent and user may have overlooked during discussion.
delivery-manager
Delivery manager for backlog shaping, project planning, release readiness, rollback planning, and maintenance coordination.