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/amanvarshney01/create-better-t-stack/triage-labelsgit clone --depth 1 https://github.com/AmanVarshney01/create-better-t-stackWrote 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/amanvarshney01/create-better-t-stack/triage-labels)<a href="https://agentmods.dev/agents/amanvarshney01/create-better-t-stack/triage-labels"><img src="https://agentmods.dev/badge/agents/amanvarshney01/create-better-t-stack/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.00207 |
| Opus 5 | $0.00000 | $0.00103 |
| Sonnet 5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00021 |
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.
This is a copy
73% identical to triage — 8 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, use the corresponding label string from this table.
Edit the right-hand column to match the vocabulary this repo actually uses.
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 · 16 lines · 0 tokens per session scan A 0db343c57c41
triage-labels is an agent published in the GitHub repository AmanVarshney01/create-better-t-stack (5,695 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 207 tokens. A static security scan graded it A with 0 findings. It is 73% identical to triage, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
CLAUDE
AI agents that handle customer conversations autonomously. Powered by Mastra, using a workspace-based architecture where agents interact through a virtual filesystem and CLI commands.
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
The skills speak in terms of five canonical triage roles. On this repo the tracker is the dev-3.0 Kanban board (see docs/agents/issue-tracker.md), so each role is a dev3 label applied to the task. dev3 statuses/columns (todo, in-progress, user-questions, review-by-ai, review-by-user) are managed by hooks and are NOT…
product-manager
Turns a raw idea or vague request into scoped user stories with acceptance criteria. Use proactively when the request describes a problem rather than a change, when scope is unclear, when priorities conflict, or before any spec or implementation work begins.
issue-tracker
GitHub Issues and the linked GitHub Project hold live work state. Local Markdown files hold synchronized briefs, decisions, evidence, and handoffs.
sweep-scan
You are a backlog sweeper. ./input.json names one repo and the exact source tree to read it against.