Borrowing it
Nothing to install: this file belongs to Piyush8296/claude-workspace. 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/Piyush8296/claude-workspace/main/.claude/commands/pr-review.mdgit clone --depth 1 https://github.com/Piyush8296/claude-workspaceWrote 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/commands/piyush8296/claude-workspace/pr-review)<a href="https://agentmods.dev/commands/piyush8296/claude-workspace/pr-review"><img src="https://agentmods.dev/badge/commands/piyush8296/claude-workspace/pr-review/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/commands/piyush8296/claude-workspace/pr-review"><img src="https://agentmods.dev/badge/commands/piyush8296/claude-workspace/pr-review.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.00008 | $0.00465 |
| Opus 5 | $0.00004 | $0.00233 |
| Sonnet 5 | $0.00002 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
pr-review 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 10d 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
PR Review
Review current branch: $ARGUMENTS
Instructions
1. Gather context
# Current branch
git branch --show-current
# Commits ahead of main
git log main..HEAD --oneline
# Changed files
git diff main --name-only
# Full diff
git diff main --stat
2. Run automated checks
# Lint all changed files
git diff main --name-only --diff-filter=ACMR | grep -E '\.(ts|tsx)$' | xargs npx eslint --no-error-on-unmatched-pattern 2>/dev/null
# Type check
npx tsc --noEmit
# Run tests related to changed files
git diff main --name-only --diff-filter=ACMR | grep -E '\.(ts|tsx)$' | xargs npx vitest related --run 2>/dev/null
3. Review changes
For each changed file, check:
- Does this change do what the commit messages claim?
- Are there any leftover
console.log,TODO, ordebuggerstatements? - Is error handling complete?
- Are there new components missing tests?
- Are accessibility requirements met?
- Any performance concerns (bundle size, re-renders)?
4. Generate PR description
Produce a PR description in this format:
## What
[One-line summary of the change]
## Why
[Context: ticket link, user problem, technical motivation]
## How
[Implementation approach, key decisions made]
## Testing
- [ ] Unit tests added/updated
- [ ] Manual testing completed
- [ ] Accessibility verified
- [ ] Edge cases covered
## Screenshots
[If UI changes, note that screenshots should be added]
5. Verdict
End with one of:
- READY — Good to create PR
- NEEDS WORK — List specific items to address first
- CONCERN — Architectural or scope concern to discuss
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.
- 10d ago First seen · 82 lines · 8 tokens per session scan A 339238232ca9
pr-review is a command published in the GitHub repository Piyush8296/claude-workspace (2 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 465 once invoked, about $0.0000 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 commands, from other repositories
review-branch
Review an existing branch holistically before merging — blast radius, conventions, security, and spec compliance.
pr
Open a Pull Request on GitHub following team conventions. Draft by default.
generate-linear-worklog
You are tasked with generating a technical work log comment for a Linear issue based on recent git commits.
add-changelog
Generate and maintain project changelog.
git-status
Command "git-status" from qdhenry/Claude-Command-Suite, covering git status command and instructions.
changelog-demo-command
Command "changelog-demo-command" from qdhenry/Claude-Command-Suite, covering demo command for changelog and instructions.