Borrowing it
Nothing to install: this file belongs to vscarpenter/gsd-task-manager. 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/vscarpenter/gsd-task-manager/main/.claude/commands/triage-prs.mdgit clone --depth 1 https://github.com/vscarpenter/gsd-task-managerWrote 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/vscarpenter/gsd-task-manager/triage-prs)<a href="https://agentmods.dev/commands/vscarpenter/gsd-task-manager/triage-prs"><img src="https://agentmods.dev/badge/commands/vscarpenter/gsd-task-manager/triage-prs/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.
<a href="https://agentmods.dev/commands/vscarpenter/gsd-task-manager/triage-prs"><img src="https://agentmods.dev/badge/commands/vscarpenter/gsd-task-manager/triage-prs.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00155 |
| Opus 5.5 | $0.00010 | $0.00062 |
| Sonnet 5.5 | $0.00005 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
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 1mo 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.
What it actually says
/triage-prs
Stop without checking out, building, testing, or modifying any pull-request branch.
The local night-shift remediation loop is retired. A same-repository branch name does not establish trust, and maintainer credentials must never be inherited by branch-controlled code.
The remaining scheduled wrapper performs read-only discovery only. Re-enabling remediation requires an exact configured bot identity, an immutable head-SHA attestation, and an ephemeral credential-free runner. Outputs from that runner must return through a separately reviewed handoff.
Report: DISABLED: local branch remediation is retired.
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.
- 1mo ago Changed · -18 lines · -30 tokens per session fd72afcba5bf
- 2mo ago First seen · 38 lines · 54 tokens per session scan A 055ae3efbd65
triage-prs is a command published in the GitHub repository vscarpenter/gsd-task-manager (40 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 155 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.
Other commands, from other repositories
preflight
Diagnostique l'environnement Cortex et guide la réparation (DB, extensions, modèles).
release
A typical CI release creates the release, associates commits, finalizes it, and records a deploy. The sentry release create examples above show the full sequence.
code-mappings
Command "code-mappings" from getsentry/sentry-mcp, covering examples, upload code mappings from a json file, specify repository explicitly, specify repository and default branch and output as json.
umt-doctor
Diagnose UMT MCP server setup — builds, environment variables, and config health.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.