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

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.

It gives issue review a repeatable process and can connect reported problems with release planning and structured tasks.

How dgunning/edgartools configures Claude Code

About the project

EdgarTools is a Python library that turns SEC EDGAR filings into structured, typed data, including financial statements, insider trades, fund holdings, and other filing types. It is used to analyze regulatory filings in notebooks, data pipelines, and AI systems. Its catalogue add-ons operate the library through skills, commands, instructions, and an MCP server.

dgunning/edgartools · 2,837 stars · on GitHub · edgartools.readthedocs.io

Reuse

Borrowing it

Nothing to install: this file belongs to dgunning/edgartools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/dgunning/edgartools/main/.claude/commands/triage.md

Clone the repo

git clone --depth 1 https://github.com/dgunning/edgartools

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/dgunning/edgartools/triage/github.svg)](https://agentmods.dev/commands/dgunning/edgartools/triage)

Your own site

<a href="https://agentmods.dev/commands/dgunning/edgartools/triage"><img src="https://agentmods.dev/badge/commands/dgunning/edgartools/triage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/dgunning/edgartools/triage"><img src="https://agentmods.dev/badge/commands/dgunning/edgartools/triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00020	$0.02354
Opus 5.5	$0.00008	$0.00942
Sonnet 5.5	$0.00004	$0.00471
Haiku 4.5	$0.00002	$0.00235

Measured 2mo ago against content hash 87e963bd4e6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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:

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

For Feature Requests:

Product-Manager Priority Scoring: Using formula (User Value × Urgency × Feasibility) / Effort
Roadmap Placement: HIGH (>20), MEDIUM (10-20), LOW (5-10), DEFER (<5)
Beads Issue Creation: bd create --external-ref 'gh:XXX' --priority P1/P2/P3 --labels feature
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.

2mo 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,837 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 2,354 once invoked, about $0.0001 per session on Opus 5.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.

10-k 10-q Project management balance-sheet edgar filings financials

triage next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
triagedgunning/edgartools	Command	2.8k	yesterday	MIT	A	20	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code
speckit.bug.fixgithub/spec-kit	Command	148k	yesterday	MIT	A	12	Claude Code

edgartools: Command for Claude Code