triage-issues

triage-issues is a command for coding agents from rohitg00/awesome-claude-code-toolkit. It costs 17 tokens per session (337 once invoked), scanned A, original, Apache-2.0.

A command that reviews open GitHub issues and sorts them by urgency, type, completeness, and likely impact. GitHub issues are records used to track bugs, feature requests, and other work.

In plain words
What is it for?
Use it to review open issues, suggest labels and priorities, identify duplicates, group related reports, flag issues needing more details, and prepare a backlog for the next sprint.
Why use it?
It helps turn an unstructured issue list into a clearer backlog by finding duplicates, stale reports, missing information, and related work. It suggests changes without closing issues or overriding existing assignments.

Command

Part of the github-issue-manager plugin — 2 commands shipped together

About the project

Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.

rohitg00/awesome-claude-code-toolkit · 2,587 stars · on GitHub

Install

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.

agentmods
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/triage-issues
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit

Or install github-issue-manager, the plugin that ships this one along with the rest of its 2 commands.

Wrote 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.

agentmods badge for triage-issues

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/triage-issues.svg)](https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/triage-issues)
Your own site
<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/triage-issues"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/triage-issues.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 337 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00337
Opus 5 $0.00009 $0.00169
Sonnet 5 $0.00003 $0.00067
Haiku 4.5 $0.00002 $0.00034

Measured yesterday against content hash e7680ec4c36d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

triage-issues 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 yesterday.

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.

plugins/github-issue-manager/commands/triage-issues.md · 34 lines

What it actually says

/triage-issues - Triage GitHub Issues

Analyze and triage open GitHub issues for prioritization.

Steps

  1. Fetch all open issues from the repository using the GitHub API
  2. Filter issues by: unlabeled, unassigned, or stale (no activity in 30 days)
  3. Analyze each issue for: completeness, reproducibility, severity, and impact
  4. Suggest labels based on issue content: bug, feature, enhancement, documentation, question
  5. Assess priority based on: user impact, frequency of reports, component affected
  6. Identify duplicate issues by comparing titles and descriptions with existing issues
  7. Flag issues that need more information from the reporter
  8. Group related issues that could be addressed together
  9. Suggest assignees based on the component or area affected
  10. Create a triage summary: total open, by priority, by label, stale issues
  11. Recommend which issues to close (duplicates, won't fix, cannot reproduce)
  12. Generate a prioritized backlog view for the next sprint

Rules

  • Do not close issues without user confirmation
  • Respect existing labels and assignments; suggest changes, do not override
  • Mark issues as stale only if truly inactive (no comments, no linked PRs)
  • Prioritize bugs over features, security issues over all others
  • Consider the number of thumbs-up reactions as a popularity signal
  • Do not auto-assign issues; suggest assignees for human decision
  • Keep triage notes factual and neutral in tone
Changes

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.

  1. yesterday First seen · 34 lines · 17 tokens per session scan A e7680ec4c36d

Subscribe to this mod's changes

triage-issues is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,587 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 337 once invoked, about $0.0001 per session on Opus 5. 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-09-03.