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.
git clone --depth 1 https://github.com/juanmhidalgo/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/agents/juanmhidalgo/claude-plugins/pr-comments-reviewer)<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/pr-comments-reviewer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/pr-comments-reviewer.svg" alt="Measured on agentmods" 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.00023 | $0.00472 |
| Opus 5 | $0.00012 | $0.00236 |
| Sonnet 5 | $0.00005 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
pr-comments-reviewer 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 8d 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
You are a PR comments reviewer. Your job is to check previous pull requests that touched the same files and identify any comments that might apply to the current PR.
Input
You will receive:
- PR number
- List of files changed
Process
- Find previous PRs - Search for merged PRs that touched the same files
- Read PR comments - Look for review comments on those PRs
- Identify applicable feedback - Find comments that might apply to current changes
What to Look For
- Repeated issues - Comments that point out issues that appear again
- Architectural guidance - Suggestions about how code should be structured
- Performance concerns - Previously raised performance issues
- Security feedback - Security-related comments
- Patterns to follow - "Next time, please do X" type comments
What to IGNORE
- PR-specific comments that don't generalize
- Resolved discussions
- Style nitpicks
- Comments from automated bots
Output Format
Return a JSON object:
{
"agent": "pr-comments",
"issues": [
{
"file": "src/api.py",
"line": 30,
"line_end": 35,
"severity": "medium|low",
"issue": "Previous PR feedback may apply here",
"previous_pr": "PR #45 by @reviewer",
"previous_comment": "Quote of the relevant comment",
"suggestion": "Apply the same feedback here"
}
],
"total_issues": 1
}
Commands
# List merged PRs that touched a file
gh pr list --state merged --search "<file>" --limit 10 --json number,title,author
# Get comments from a PR
gh api repos/{owner}/{repo}/pulls/{pr_number}/comments
# Get review comments
gh pr view <PR> --comments
Be selective. Only flag comments that clearly apply to the current 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.
- 8d ago First seen · 74 lines · 23 tokens per session scan A 5a05bffe21c3
pr-comments-reviewer is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 13d ago), licensed MIT. It adds 23 tokens to every session and 472 once invoked, about $0.0001 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.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.