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 cblecker/claude-plugins --skill triage-prsgit clone --depth 1 https://github.com/cblecker/claude-pluginsWrote 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/cblecker/claude-plugins/triage-prs)<a href="https://agentmods.dev/skills/cblecker/claude-plugins/triage-prs"><img src="https://agentmods.dev/badge/skills/cblecker/claude-plugins/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/skills/cblecker/claude-plugins/triage-prs"><img src="https://agentmods.dev/badge/skills/cblecker/claude-plugins/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.00083 | $0.02916 |
| Opus 5.5 | $0.00033 | $0.01166 |
| Sonnet 5.5 | $0.00017 | $0.00583 |
| Haiku 4.5 | $0.00008 | $0.00292 |
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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage PRs
Investigate open PRs that need your attention in the target repo, then present batched triage with options to unassign, remove review requests, or unsubscribe.
Tool names below are short forms of the allowed-tools entries (get_me → mcp__plugin_github_github__get_me).
Repo Context
- Repo argument (overrides remote detection if non-empty): $ARGUMENTS
- Detected remote: !
git remote get-url upstream 2>/dev/null || git remote get-url origin 2>/dev/null || echo __NO_REMOTE__
Phase 1: Setup
Repo identity: if the repo argument above is non-empty, parse it as OWNER/REPO. Otherwise parse the detected remote URL — SSH ([email protected]:OWNER/REPO.git) or HTTPS (https://github.com/OWNER/REPO). If it is __NO_REMOTE__ and no argument was given, print "No GitHub remote detected — re-run as /github:triage-prs owner/repo." and stop.
Authenticated user: call get_me → store login as USERNAME.
Phase 2: Collect and Classify
Run four searches in parallel (paginate with perPage: 100 if truncated):
search_pull_requests(query: "assignee:@me is:open", owner, repo) # role: assigned
search_pull_requests(query: "review-requested:@me is:open", owner, repo) # role: reviewer
search_pull_requests(query: "commenter:@me is:open", owner, repo) # engagement
search_pull_requests(query: "reviewed-by:@me is:open", owner, repo) # engagement
Candidates are the union of the first two searches, deduplicated by PR number and tagged with roles assigned, reviewer, or both. A candidate is engaged if its number appears in either engagement search.
Notification lookup (used here and in Phase 5): call list_notifications(owner, repo, filter: "include_read_notifications") once per phase — read notifications are excluded by default — paginate all pages, and match threads by the PR their subject.url points at.
Sweep stale closed-PR notifications: take PullRequest-type threads from the lookup whose PR number is not among the candidates. For each, call pull_request_read(method: "get"); if that PR is closed or merged, dismiss_notification(threadID, state: "done") — dismiss only, never ignore, so a reopened PR still notifies you. Threads whose PR is still open stay untouched.
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 First seen · 179 lines · 83 tokens per session scan A 04eb87a7f8b9
triage-prs is a skill published in the GitHub repository cblecker/claude-plugins (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 83 tokens to every session and 2,916 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-31.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…