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.
npx skills add OutThisLife/brooklyn-skills --skill pr-triagegit clone --depth 1 https://github.com/OutThisLife/brooklyn-skillsWrote 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/skills/outthislife/brooklyn-skills/pr-triage)<a href="https://agentmods.dev/skills/outthislife/brooklyn-skills/pr-triage"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/pr-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.
<a href="https://agentmods.dev/skills/outthislife/brooklyn-skills/pr-triage"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/pr-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00069 | $0.04318 |
| Opus 5.5 | $0.00028 | $0.01727 |
| Sonnet 5.5 | $0.00014 | $0.00864 |
| Haiku 4.5 | $0.00007 | $0.00432 |
Grade A, and why
pr-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 28d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Triage
Maintainer triage. Three real outcomes: approve, supersede (salvage +
credit + close the old one), or close (wrong premise). Verdict first; wait
for an explicit go before forge writes (approve / supersede / close / merge /
push). Use gh or glab.
Explicit review scope
Treat the user's stated outcome set as overriding the default taxonomy below. If they request approve or request changes only, review each MR on that basis: report concrete blockers as request changes, and do not consolidate, supersede, close, or implement a replacement. Keep the verdict-first / explicit-go boundary for forge writes.
Kickoff
Batch ("we will be reviewing…") or a pasted Discord/>>>…<<< thread with a PR:
- Figure out repo + forge. Skim
AGENTS.md/CONTRIBUTING.mdif present. - Match this repo's worktree/branch naming by inspecting existing worktrees.
- Don't touch the primary checkout — use worktrees.
- Cluster the batch first (below), then verdict + salvage plan; wait for go before forge writes.
Cluster the batch first (before per-PR verdicts)
More than one PR/issue in front of you? Group them by the fix they need before you judge any single one. Multiple PRs on the same bug (or fragile subsystem) are one consolidation, not N salvages.
- Map each PR/issue to the underlying fix and the files/subsystem it touches.
- Any two that fix the same bug class or the same subsystem → treat the
group as one super-PR: build the proper fix once, credit every
author (
Co-authored-by+@handle), and supersede the whole cluster. - Default to consolidation. Only keep PRs separate when the fixes are genuinely independent (different bug class, different area, no shared code).
- State the grouping up front, e.g.
#68665 + #63590 + #67603 → one super-PR, then run the per-PR loop within each group to confirm premises.
Do not enumerate one verdict per PR when they share a fix — that's the lazy shape. One cluster → one consolidated supersede.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 28d ago Changed · +2 lines 949156195d54
- 1mo ago Changed · +5 lines 1fe8dad972fa
- 1mo ago Changed · +57 lines 93e3808f3909
- 2mo ago First seen · 214 lines · 69 tokens per session scan A 96627fc93bf5
pr-triage is a skill published in the GitHub repository OutThisLife/brooklyn-skills (209 stars, last pushed 7d ago), licensed MIT. It adds 69 tokens to every session and 4,318 once invoked, about $0.0003 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 skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…