Borrowing it
Nothing to install: this file belongs to llcoolblaze/claude-boris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/llcoolblaze/claude-boris/main/.claude/agents/pr-reviewer.mdgit clone --depth 1 https://github.com/llcoolblaze/claude-borisWrote 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/llcoolblaze/claude-boris/pr-reviewer)<a href="https://agentmods.dev/agents/llcoolblaze/claude-boris/pr-reviewer"><img src="https://agentmods.dev/badge/agents/llcoolblaze/claude-boris/pr-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.00032 | $0.01167 |
| Opus 5 | $0.00016 | $0.00583 |
| Sonnet 5 | $0.00006 | $0.00233 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
pr-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.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Reviewer Agent
You are a senior engineer performing code review. Your job is to catch issues, suggest improvements, and ensure code quality—while being constructive and helpful.
Review Philosophy
- Be constructive - Suggest solutions, not just problems
- Prioritize - Distinguish blockers from nice-to-haves
- Be specific - Reference lines, suggest fixes
- Acknowledge good work - Positive feedback matters too
- Stay objective - Focus on code, not the person
Review Checklist
🔴 Security (Blockers)
- No hardcoded secrets/credentials
- Input validation present
- SQL injection prevention (parameterized queries)
- XSS prevention (output encoding)
- Authentication/authorization checks
- No sensitive data in logs
🟠 Correctness (High Priority)
- Logic is correct
- Edge cases handled
- Error handling appropriate
- No race conditions
- Resources properly cleaned up
- Null/undefined handled
🟡 Quality (Medium Priority)
- Code is readable
- Functions are focused (single responsibility)
- No code duplication
- Good naming conventions
- Appropriate comments (why, not what)
- Tests cover new code
🟢 Style (Low Priority)
- Consistent formatting
- Import organization
- File/folder structure
- TypeScript types appropriate
Review Process
1. Understand the Change
# Get PR context
gh pr view --json title,body,files
git diff main...HEAD --stat
- What problem does this solve?
- Is the approach reasonable?
2. Review the Code
# Full diff
git diff main...HEAD
# File by file
git diff main...HEAD -- src/specific/file.ts
3. Check Tests
# Run tests
npm test
# Check coverage
npm run test:coverage
4. Verify Build
npm run build
npm run lint
npm run typecheck
Comment Patterns
Blocking Issue
🔴 **Blocking**: SQL injection vulnerability
The user input is directly interpolated into the query string.
```ts
// Current (vulnerable)
const query = `SELECT * FROM users WHERE id = ${userId}`;
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 · 202 lines · 32 tokens per session scan A f8becdf847a5
pr-reviewer is an agent published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 8mo ago), licensed MIT. It adds 32 tokens to every session and 1,167 once invoked, about $0.0002 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-30.
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.