pr-analyzer

pr-analyzer is an agent for Claude Code from Sagargupta16/claude-skills. It costs 91 tokens per session (421 once invoked), scanned A, original, MIT.

An agent that reviews GitHub pull requests and reports their health. It checks automated tests, review comments, approvals, merge status, and other requirements for merging.

In plain words
What is it for?
Use it to check open pull requests, distinguish code failures from infrastructure failures, find unresolved comments, and decide whether to fix, rebase, or request approval.
Why use it?
It gathers scattered pull-request information in one assessment and identifies what is still blocking a merge.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the oss-contrib plugin — 1 skill, 2 commands, 1 agent shipped together

Good fit Use it to check open pull requests, distinguish code failures from infrastructure failures, find unresolved comments, and decide whether to fix, rebase, or request approval.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/sagargupta16/claude-skills/pr-analyzer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Sagargupta16/claude-skills

Made for: Claude Code.

Or install oss-contrib, the plugin that ships this one along with the rest of its 1 skill, 2 commands, 1 agent.

Wrote 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.

agentmods badge for pr-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/sagargupta16/claude-skills/pr-analyzer/github.svg)](https://agentmods.dev/agents/sagargupta16/claude-skills/pr-analyzer)
Your own site
<a href="https://agentmods.dev/agents/sagargupta16/claude-skills/pr-analyzer"><img src="https://agentmods.dev/badge/agents/sagargupta16/claude-skills/pr-analyzer/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.

agentmods 80×15 button for pr-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/agents/sagargupta16/claude-skills/pr-analyzer"><img src="https://agentmods.dev/badge/agents/sagargupta16/claude-skills/pr-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 421 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.00421
Opus 5 $0.00046 $0.00211
Sonnet 5 $0.00018 $0.00084
Haiku 4.5 $0.00009 $0.00042

Measured 9d ago against content hash 232d5d994944, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

pr-analyzer 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 9d 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.

plugins/oss-contrib/agents/pr-analyzer.md · 39 lines

What it actually says

You are a PR analysis specialist. Check PR health, CI status, and review state.

Process

  1. Get PR details:

    • gh api repos/{owner}/{repo}/pulls/{num} for merge state, draft status, labels
    • gh api repos/{owner}/{repo}/pulls/{num}/reviews for review decisions
    • gh api repos/{owner}/{repo}/issues/{num}/comments for discussion
    • gh api repos/{owner}/{repo}/pulls/{num}/comments for inline review comments
  2. Check CI status:

    • gh api repos/{owner}/{repo}/commits/{sha}/check-runs for check results
    • Identify failing checks and their error messages
    • Distinguish between: our code failures vs infrastructure/bot failures
  3. Assess merge readiness:

    • Mergeable state (clean, blocked, behind)
    • Required reviews met?
    • All required checks passing?
    • How far behind base branch?
  4. Identify action items:

    • Unresolved review comments
    • Failing CI that needs fixing
    • Rebase needed if behind
    • Missing required labels or approvals

Output Format

PR Status CI Reviews Action Needed
repo#num Mergeable/Blocked Passing/Failing Approved/Pending Next step
Changes

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.

  1. 9d ago First seen · 39 lines · 91 tokens per session scan A 232d5d994944

Subscribe to this mod's changes

pr-analyzer is an agent published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 91 tokens to every session and 421 once invoked, about $0.0005 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-31.