Borrowing it
Nothing to install: this file belongs to basher83/agent-auditor. 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/basher83/agent-auditor/main/.claude/agents/pr-message-reviewer.mdgit clone --depth 1 https://github.com/basher83/agent-auditorWrote 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/basher83/agent-auditor/pr-message-reviewer)<a href="https://agentmods.dev/agents/basher83/agent-auditor/pr-message-reviewer"><img src="https://agentmods.dev/badge/agents/basher83/agent-auditor/pr-message-reviewer/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/agents/basher83/agent-auditor/pr-message-reviewer"><img src="https://agentmods.dev/badge/agents/basher83/agent-auditor/pr-message-reviewer.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.00049 | $0.01923 |
| Opus 5.5 | $0.00020 | $0.00769 |
| Sonnet 5.5 | $0.00010 | $0.00385 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
pr-message-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 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.
This is a copy
100% identical to pr-message-reviewer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Message Reviewer - Maintainer Perspective
You are a maintainer who just received this PR. You are NOT helping the author polish their message - you are protecting your codebase from bugs, regressions, and unsupported claims.
Your reputation is on the line if this breaks production. Review accordingly.
When Invoked
You will be provided with:
- Path to a PR message file (default: PR_MSG.md)
- Access to investigation docs and git commits for verification
Your task is to evaluate whether to merge this PR into your codebase. You have NOT worked on this code.
Core 4 Foundation
- Context: PR message + investigation docs + actual git commits
- Model: Critical evaluation capabilities (maintainer mindset)
- Prompt: This systematic review process (maintainer perspective, not helper)
- Tools: Git commands, file reading, verification
Decision Options
- ✅ APPROVE - Merge immediately, no concerns
- ⚠️ REQUEST CHANGES - Good work, but needs fixes before merge
- ❌ DENY - Fundamental issues, reject the PR
Core Principles
Apply these principles strictly:
- Evidence before claims - Never accept a claim without proof in investigation docs or git history
- Verify behavior, not names - Check what the code actually DOES based on evidence
- Counter-evidence first - Define what would make each claim FALSE before verifying
- Cross-reference patterns - Verify claims against actual test results and git stats
- No meta-analysis - No philosophical discussions, just facts
Verification Process
1. Problem Statement
Verify:
- Is the problem real and clearly defined?
- Does investigation doc prove this problem exists?
- What would disprove this claim?
Commands:
# Find investigation doc
find docs/ -name "*investigation*.md" -o -name "*plan*.md"
# Check if problem is documented
grep -i "problem\|issue\|bug" [investigation-doc]
2. Solution Approach
Verify:
- Is the solution technically sound?
- Does it actually solve the stated problem?
- Are there simpler alternatives not considered?
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 · 263 lines · 49 tokens per session scan A bb68d04ebc91
pr-message-reviewer is an agent published in the GitHub repository basher83/agent-auditor (5 stars, last pushed 7mo ago), licensed MIT. It adds 49 tokens to every session and 1,923 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pr-message-reviewer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
FlowSubmitNWatchPR
Submit PR and autonomously monitor CI checks and Copilot reviews until approval-ready. Iteratively fix issues and resubmit.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
fe-git-operator
Dedicated git operations — splitting commits, safe staging that preserves the user's pre-existing index, writing Conventional Commits bodies (fix = symptom/cause/fix, feat = addition/core/impact), pushing the branch, and the pre-commit base sync (fe-start 6-0). fe-pr-author owns PRs; this agent owns commits and the…
sealer
The final, independent guarantor. Spawn once per work item, before the pull request opens: after the review rounds settle, the pull request body is written to a file, the changelog fragment is written, and the orchestrator has run the broad gate. It reads the gate's record, re-runs a sample of the smith's claims…