A repository command for reviewing open GitHub issues and deciding their type, priority, affected component, and next action.

Use it to label, comment on, link, close, and assign open issues, including marking suitable issues as good first issues.

It turns an unorganised issue list into consistent decisions, identifies duplicate reports, and highlights issues that need more information.

triage — Command for Claude Code by mizukaizen

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.

Clone the repo

git clone --depth 1 https://github.com/mizukaizen/hive-doctrine-mcp

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/mizukaizen/hive-doctrine-mcp/triage/github.svg)](https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/triage)

Your own site

<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/triage"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/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/mizukaizen/hive-doctrine-mcp/triage"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 545 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.00000	$0.00545
Opus 5	$0.00000	$0.00272
Sonnet 5	$0.00000	$0.00109
Haiku 4.5	$0.00000	$0.00055

Measured 12d ago against content hash f629240ca576, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 12d 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.

gated-products/honey/claude-packages/HD-4003-oss-maintainer/commands/triage.md · 72 lines

How it starts

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

Command: /triage

Systematically triage open issues in the repository.

Usage

/triage

Process

Step 1: Gather Open Issues

List all open issues without labels or with the needs-triage label. Sort by creation date (oldest first).

# If using GitHub CLI
gh issue list --state open --label "needs-triage" --limit 50
# Or list unlabelled issues
gh issue list --state open --limit 50 --json number,title,labels,createdAt

Step 2: For Each Issue, Determine

Type: bug / feature / docs / question / duplicate
Priority: critical / high / medium / low
Component: which part of the project is affected
Actionability: Can someone act on this now, or is more info needed?
First issue: Is this suitable for good first issue labelling?

Step 3: Check for Duplicates

For each issue, search existing issues (open and closed) for similar reports:

gh issue list --state all --search "[key terms from issue]" --limit 10

If a duplicate is found, link the original and close the duplicate with a polite message.

Step 4: Apply Labels and Respond

For each triaged issue:

Apply appropriate labels
Add a comment acknowledging the report
Assign to a milestone if appropriate
If more info is needed, ask specific questions (not "can you provide more info?")

Step 5: Generate Triage Summary

# Triage Summary — [YYYY-MM-DD]

## Processed: [X] issues

| # | Title | Type | Priority | Action Taken |
|---|-------|------|----------|--------------|
| 42 | Crash on startup | bug | critical | Labelled, assigned to v2.1.1 |
| 43 | Add dark mode | feature | medium | Labelled, added to backlog |
| 44 | Typo in README | docs | low | Labelled 'good first issue' |

## Duplicates Closed: [X]
## Needs Info: [X]
## New 'Good First Issues': [X]

Rules

Process issues in chronological order. Older issues first.
Never close an issue without an explanation.
If unsure about priority, default to medium and flag for maintainer review.
Spend a maximum of 2 minutes per issue during triage. Deep investigation happens later.

Read the full file on GitHub · 72 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.

12d ago First seen · 72 lines · 0 tokens per session scan A f629240ca576

Subscribe to this mod's changes

triage is a command published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 545 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-31.

AI Safety Multi-Agent Project management agent-marketplace ai-agents mcp mcp-server

mega-status

Show detailed status of mega-plan execution including feature progress and story completion. Usage: /plan-cascade:mega-status.

Taoidle/plan-cascade · 23 tokens

hybrid-status

Show execution status of all stories in the PRD. Displays batch progress, individual story states, completion percentage, and recent activity logs.

Taoidle/plan-cascade · 27 tokens

hybrid-complete

Complete Hybrid Ralph task in worktree, verify all stories complete, commit code changes (excluding planning files), merge to target branch, and cleanup worktree directory. Can be run from any directory.

Taoidle/plan-cascade · 39 tokens

status