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 FlorianBruniaux/claude-code-plugins --skill pr-triagegit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-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/florianbruniaux/claude-code-plugins/pr-triage)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/pr-triage"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/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/florianbruniaux/claude-code-plugins/pr-triage"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/pr-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 576 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00086 | $0.05310 |
| Opus 5.5 | $0.00034 | $0.02124 |
| Sonnet 5.5 | $0.00017 | $0.01062 |
| Haiku 4.5 | $0.00009 | $0.00531 |
Grade A, and why
pr-triage scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Use `gh` CLI (not `curl` GitHub API) except for collaborators list How it starts
The opening of the file, as written. The whole thing — 626 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Triage
4-phase workflow for maintainers: automated audit of all open PRs, opt-in deep review via parallel agents, validated comment posting, and optional worktree setup for local review.
When to Use This Skill
| Skill | Usage | Output |
|---|---|---|
/pr-triage |
Sort, review, and comment on a PR backlog | Triage table + reviews + posted comments |
/review-pr |
Review a single PR in depth | Inline PR review |
Triggers:
- Manually:
/pr-triageor/pr-triage allor/pr-triage 42 57 - Proactively: when >5 PRs open without review, or stale PR >14 days detected
Language
- Check the argument passed to the skill
- If
enorenglish→ tables and summary in English - If
fr,french, or no argument → French (default) - Note: GitHub comments (Phase 3) are ALWAYS in English (international audience)
Configuration
Thresholds used throughout the workflow. Edit to match your project:
| Parameter | Default | Description |
|---|---|---|
staleness_days |
14 | Days without activity before flagging as stale |
overlap_threshold |
50% | Shared files % to flag as overlapping |
cluster_min_prs |
3 | Author PR count to trigger cluster suggestion |
xl_cutoff_additions |
1000 | Additions above which a PR is classified XL |
xl_cutoff_files |
10 | Changed files above which a PR is "too large" |
Preconditions
git rev-parse --is-inside-work-tree
gh auth status
If either fails, stop and explain what is missing.
Phase 1: Audit (always executed)
Data Gathering (parallel commands)
gh repo view --json nameWithOwner -q .nameWithOwner
gh pr list --state open --limit 50 \
--json number,title,author,createdAt,updatedAt,additions,deletions,changedFiles,isDraft,mergeable,reviewDecision,statusCheckRollup,body
gh api "repos/{owner}/{repo}/collaborators" --jq '.[].login'
Collaborators fallback: if gh api .../collaborators returns 403/404:
gh pr list --state merged --limit 10 --json author --jq '.[].author.login' | sort -u
If still ambiguous, ask via AskUserQuestion.
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.
- 1mo ago First seen · 626 lines · 86 tokens per session scan A e1bc9c943c3b
pr-triage is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (42 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 5,310 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
pr-review
Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first.
feedback-builder
Point Aeon at a service's /feedback endpoint - pull what agents reported (bugs, missing features), triage and cluster it, then build the best accepted request as a PR for a human to approve.
pr-triage
First-touch triage for external pull requests - verdict, label, and a welcoming comment within minutes of open.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
pr-description
Write or update a GitHub PR description as a short, skimmable list of key points grounded in the diff and real verification. Use when opening a PR or editing its description.
nox-review
Run an adversarial review of a code diff or a plan artifact under a second AI harness, headlessly, from an ephemeral git worktree with the repository's own instruction, hook and credential files removed. Use when a change needs a reviewer that did not write it, when a cross-model second opinion is wanted before…