A command for classifying and labelling newly opened GitHub issues. Issues are work reports or requests, and labels group them by type, priority, area, provider, or platform.

Use it to scan a chosen number of recent days, skip already triaged issues, and assign labels such as bug, priority, component, provider, or platform.

It finds recent open issues without the required labels and applies the project's classification rules. This keeps incoming work easier to sort and review.

triage — Command by can1357

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/can1357/oh-my-pi/triage

Clone the repo

git clone --depth 1 https://github.com/can1357/oh-my-pi

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 1,318 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01318
Opus 5	$0.00000	$0.00659
Sonnet 5	$0.00000	$0.00264
Haiku 4.5	$0.00000	$0.00132

Measured yesterday against content hash d460f7b290ad, 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 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.

.omp/commands/triage.md · 112 lines

How it starts

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

Triage Command

Classify/label newly opened GitHub issues missing labels.

Arguments

$ARGUMENTS: optional --days <n>; default 7. Triage only open issues created within this window.

Steps

1. Fetch

Parse $ARGUMENTS for --days (default 7).

# Build cutoff date (UTC) for "new" issues
CUTOFF_DATE="$(python - <<'PY'
from datetime import datetime, timedelta, timezone
print((datetime.now(timezone.utc) - timedelta(days=7)).strftime('%Y-%m-%d'))
PY
 )"

# Fetch only newly created open issues (default 7-day window)
gh issue list --state open --search "created:>=${CUTOFF_DATE}" --json number,title,body,labels,comments,createdAt --limit 50

2. Candidates

Skip issues older than cutoff or labeled triaged. Of the rest, skip only if all applicable requirements hold:

Exactly one primary: bug|enhancement|question|proposal|documentation|invalid|duplicate.
bug → exactly one prio:*.
Applicable functional scope → at least one: agent|tool|tui|cli|prompting|sdk|auth|setup|ux|providers.
Provider-specific → matching provider:*; platform-specific → matching platform:*.

3. Classification

For every candidate, read title, body, and all comments; comments may contain critical context. Labels below; primary exactly one, priority exactly one only for bug, functional all applicable. Provider/platform labels require explicit issue evidence.

Primary

bug: broken existing behavior—crash, error, regression, "doesn't work".
enhancement: feature request/improvement to existing behavior.
question: how-to, clarification, usage question.
proposal: design/process proposal needing maintainer decision.
documentation: missing, incorrect, outdated docs.
invalid: spam, off-topic, not actionable.
duplicate: clear duplicate; reference original in a comment.

Bug priority

prio:p0: critical blocker, data loss/security breakage, unusable workflow.
prio:p1: high impact, common workflow broken, fix soon.
prio:p2: medium impact, workaround exists, not blocking most users.
prio:p3: low impact, edge case/minor issue.

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

yesterday First seen · 112 lines · 0 tokens per session scan A d460f7b290ad

Subscribe to this mod's changes

triage is a command published in the GitHub repository can1357/oh-my-pi (28,439 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,318 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.

Data and AI Debugging Frontend LLM ai-agent bun cli coding-assistant typescript

triage

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Triage Command

Arguments

Steps

1. Fetch

2. Candidates

3. Classification

What this file has done since we first saw it

Other commands, from other repositories

maintainer-standup

create-command

execute

handoff

plan-feature

system-review