agentmods.dev

llm-wiki: Command for Claude Code

.claude/commands/triage-issue.md

triage-issue is a command for Claude Code from Pratiyush/llm-wiki. It costs 0 tokens per session (848 once invoked), scanned A, original, MIT.

An issue-triage command for the llmwiki code repository. Triage means sorting a new issue by type, urgency, and the part of the project it affects.

In plain words
What is it for?
It fetches an issue, searches for related reports, reads the repository rules, and applies labels, a milestone, and a priority when appropriate.
Why use it?
It gives new issues consistent labels and checks for duplicates or proposals that were previously declined.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is Pratiyush/llm-wiki's own configuration. It tells Claude Code how to work on llm-wiki itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything llm-wiki configures →

Part of the llm-wiki plugin — 6 skills, 18 commands shipped together

not rated 385repo +1 2mo ago A scan 0 tokens original MIT
View source ↗ Pratiyush/llm-wiki
Reuse

Borrowing it

Nothing to install: this file belongs to Pratiyush/llm-wiki. 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/Pratiyush/llm-wiki/master/.claude/commands/triage-issue.md
Clone the repo
git clone --depth 1 https://github.com/Pratiyush/llm-wiki

Made for: Claude Code.

Or install llm-wiki, the plugin that ships this one along with the rest of its 6 skills, 18 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-issue

README.md
[![agentmods](https://agentmods.dev/badge/commands/pratiyush/llm-wiki/triage-issue.svg)](https://agentmods.dev/commands/pratiyush/llm-wiki/triage-issue)
Your own site
<a href="https://agentmods.dev/commands/pratiyush/llm-wiki/triage-issue"><img src="https://agentmods.dev/badge/commands/pratiyush/llm-wiki/triage-issue.svg" alt="Measured on agentmods" 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 848 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00848
Opus 5 $0.00000 $0.00424
Sonnet 5 $0.00000 $0.00170
Haiku 4.5 $0.00000 $0.00085

Measured 7d ago against content hash 227c8b2f2927, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

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

.claude/commands/triage-issue.md · 82 lines

How it starts

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

Apply labels + milestone + priority to a new issue using the llmwiki triage rules.

Usage: /triage-issue

This slash command loads docs/maintainers/TRIAGE.md and applies the label taxonomy to the given issue. The goal is to give every new issue a type, a priority, and a layer label within 24 hours — not to fully resolve it.

Workflow

  1. Fetch the issue — gh issue view <N> for the title, body, author, current labels, and comment count. Note whether it's actually new or a re-surfaced old issue.

  2. Read the governance docs first — load:

    • docs/maintainers/TRIAGE.md (label taxonomy + rules)
    • docs/maintainers/ARCHITECTURE.md (layer definitions)
    • docs/maintainers/DECLINED.md (check for prior rejection)
    • docs/maintainers/ROADMAP.md (current milestone themes)

  3. Check for duplicates — before labeling, run:

    gh issue list --search "<keywords from title>" --state all --limit 20

    If it's a duplicate, close the new one with a comment linking to the original and stop. Don't apply labels to a duplicate.

  4. Check DECLINED.md — if the idea has already been declined, close with a comment linking to the entry and ask the reporter what's changed since the decline. Don't silently close.

  5. Apply the required labels — every issue gets exactly one of each category:

    • Type: enhancement / bug / docs / chore / epic / question / wontfix
    • Priority: priority:must / priority:should / priority:could / priority:wont
    • Layer: layer-0 through layer-7 (required for anything actionable; question and epic can skip)

  6. Assign a milestone — for priority:must + priority:should items, assign the current release milestone from docs/maintainers/ROADMAP.md. priority:could items stay unmilestoned until a contributor picks them up.

  7. Post a triage comment — use the template below.

  8. Append to log — one line to wiki/log.md:

    ## [YYYY-MM-DD] triage | #<N>: <labels> → <milestone>

Read the full file on GitHub · 82 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. 7d ago First seen · 82 lines · 0 tokens per session scan A 227c8b2f2927

Subscribe to this mod's changes

triage-issue is a command published in the GitHub repository Pratiyush/llm-wiki (385 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 848 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-30.

Claude CodeProject managementaicodex-clicursordeveloper-toolskarpathy
Related

Other commands, from other repositories

arrange-workspace-flow-choose-workspace-layout

Phase 1 Choose Workspace Layout of arrange-workspace-flow.

griddynamics/rosetta · 22 tokens

arrange-workspace-flow

Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.

griddynamics/rosetta · 26 tokens

taskstoissues

A command that turns structured tasks from project design documents into ordered GitHub Issues, written in simplified Chinese.

loulanyue/spec-kit-zh · 24 tokens

ijfw-status

Show IJFW state -- mode, routing, memory, recent activity, codebase index, settings. Use when you want the at-a-glance banner you'd otherwise get at session start.

FerroxLabs/ijfw · 41 tokens

team

Manage your project's agent team. Usage: /team [setup|list|add|remove|swap].

FerroxLabs/ijfw · 23 tokens

arrange-workspace-flow-configure-ecosystem

Phase 6 Configure Ecosystem of arrange-workspace-flow.

griddynamics/rosetta · 22 tokens