Borrowing it
Nothing to install: this file belongs to 1broseidon/ketch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/1broseidon/ketch/main/.claude/commands/triage-prs.mdgit clone --depth 1 https://github.com/1broseidon/ketchWrote 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.
[](https://agentmods.dev/commands/1broseidon/ketch/triage-prs)<a href="https://agentmods.dev/commands/1broseidon/ketch/triage-prs"><img src="https://agentmods.dev/badge/commands/1broseidon/ketch/triage-prs.svg" alt="Measured on agentmods" height="20"></a>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.00021 | $0.00943 |
| Opus 5 | $0.00010 | $0.00472 |
| Sonnet 5 | $0.00004 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
triage-prs 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily PR & Issue Triage Loop
You are running an autonomous daily triage loop on the 1broseidon/ketch repo.
Your job: process every untriaged open PR and issue, auto-fix what is provably
low-risk, and flag everything else for human approval. Work the loop below
one item at a time. Be conservative: when in doubt, NOTIFY rather than fix.
State memory (idempotency)
The triaged label is your memory. An item carrying triaged was already
handled on a prior run — skip it unless it has new activity since that label was
applied. Apply triaged to every item only AFTER you finish handling it. This
makes the loop safe to run daily without redoing work.
DISCOVER
gh pr list --state open --json number,title,updatedAt,labels --search '-label:triaged'
gh issue list --state open --json number,title,updatedAt,labels --search '-label:triaged'
Also re-include any triaged item whose latest comment/commit is newer than the
triaged label (new human activity = re-triage). If nothing is left to process,
STOP and emit the digest (see below).
PLAN (per item)
Classify and assign a risk tier. The tier is mechanical, not a judgment call:
AUTO-FIX — only if ALL of these hold:
- typo/docs fix, lint/format, a dependency patch bump, an added missing test, OR a small localized bug fix
- the diff is tight and does NOT touch the CLI flag surface,
--json/frontmatter output format, or the config schema (config/) - the change is objectively verifiable by the test suite
NOTIFY — anything else, including: changes to CLI flags / output format / config schema / cache / crawl architecture / security; anything tests don't cover; anything large, ambiguous, or that you are unsure about.
For open PRs: review the diff. If it's a clean low-risk PR, you may leave an approving review comment but DO NOT merge. Otherwise NOTIFY.
EXECUTE
AUTO-FIX path:
git checkout -b triage/<issue-number>-<slug>offmain.- Make the minimal fix.
- Proceed to VERIFY. Only open a PR if verification is green.
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.
- 8d ago First seen · 91 lines · 21 tokens per session scan A 7bd95fd38df8
triage-prs is a command published in the GitHub repository 1broseidon/ketch (545 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 943 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.
Other commands, from other repositories
fix
Auto-fix linting, formatting, and common issues.
iterate
Work in iterations with implementation rounds followed by critical review passes.
parallelize
Split tasks among subagents for parallel execution.
align
Context-aware alignment. When in plan mode, it reviews the active plan. Otherwise, it reviews all branch changes against Ion quality gates and principles, implements the fixes and commits them after operator approval.
squash
Rebuild a feature branch into clean conventional commits while preserving its exact final tracked tree.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.