triage

A command for reviewing GitHub issues and deciding how they should be classified, prioritised, and tracked as development work.

In plain words
What is it for?
Use it on one issue, several issues, or all open issues to assess bugs, set urgency, choose a release type, create tasks, and update planning documents.
Why use it?
It gives issue review a repeatable process and can connect reported problems with release planning and structured tasks.

Command for Claude Code

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/dgunning/edgartools/triage
Clone the repo
git clone --depth 1 https://github.com/dgunning/edgartools

Made for: Claude Code.

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,354 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.00020 $0.02354
Opus 5 $0.00010 $0.01177
Sonnet 5 $0.00004 $0.00471
Haiku 4.5 $0.00002 $0.00235

Measured 2d ago against content hash 87e963bd4e6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

triage 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • triage — 100% identical, 0 lines differ
.claude/commands/triage.md · 273 lines

How it starts

The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Issue Triage Command

Use the Product Manager agent to systematically triage GitHub issues following the Issue-PM Integration Protocol. This command coordinates with issue-handler and product-manager agents to classify bugs, prioritize features, and update living documents.

Protocol: See docs-internal/planning/ISSUE-PM-INTEGRATION-PROTOCOL.md

Usage Examples

# Triage a specific issue (standard protocol workflow)
/triage 418

# Triage multiple issues
/triage 418 417 412

# Triage all open issues (batch processing)
/triage all

# Emergency triage for critical bugs (fast-track)
/triage --emergency 408

# Triage without automatic task creation
/triage --no-tasks 418

Command Implementation

I'll analyze the specified GitHub issues following the Issue-PM Integration Protocol:

For Bug Reports:

  1. Issue-Handler Coordination: Reproduction and initial assessment
  2. Product-Manager Classification: Critical vs Normal bug severity
  3. Release Type Decision: Point release (4.19.X) vs Minor release (4.20.0)
  4. Beads Issue Creation: bd create --external-ref 'gh:XXX' --priority P0/P1 --labels bug
  5. ROADMAP.md Update: Add to release planning section if needed

For Feature Requests:

  1. Product-Manager Priority Scoring: Using formula (User Value × Urgency × Feasibility) / Effort
  2. Roadmap Placement: HIGH (>20), MEDIUM (10-20), LOW (5-10), DEFER (<5)
  3. Beads Issue Creation: bd create --external-ref 'gh:XXX' --priority P1/P2/P3 --labels feature
  4. ROADMAP.md Update: Add to target version section for strategic planning

Bug Severity Classification:

Critical Bugs (Point Release 4.19.X - Immediate):

  • Data accuracy issues in financial statements
  • Core functionality blocked
  • Security vulnerabilities
  • Severe regressions from recent releases

Normal Bugs (Minor Release 4.20.0 - Scheduled):

  • Limited use case impact
  • Workaround available
  • Not data accuracy issue
  • Minor functionality impaired

Read the full file on GitHub · 273 lines

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. 2d ago First seen · 273 lines · 20 tokens per session scan A 87e963bd4e6b

Subscribe to this mod's changes

triage is a command published in the GitHub repository dgunning/edgartools (2,644 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 2,354 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-08-30.