Borrowing it
Nothing to install: this file belongs to criblio/ultra-jira-mcp. 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/criblio/ultra-jira-mcp/main/.claude/commands/review-pr.mdgit clone --depth 1 https://github.com/criblio/ultra-jira-mcpWrote 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/criblio/ultra-jira-mcp/review-pr)<a href="https://agentmods.dev/commands/criblio/ultra-jira-mcp/review-pr"><img src="https://agentmods.dev/badge/commands/criblio/ultra-jira-mcp/review-pr/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/criblio/ultra-jira-mcp/review-pr"><img src="https://agentmods.dev/badge/commands/criblio/ultra-jira-mcp/review-pr.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.00000 | $0.00210 |
| Opus 5 | $0.00000 | $0.00105 |
| Sonnet 5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
review-pr 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 11d 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
Invoke the pr-reviewer subagent via the Agent tool with subagent_type: "pr-reviewer". Pass through the user's argument as the PR identifier.
- If the user supplied a PR number in
$ARGUMENTS, tell the subagent: "Review PR #." - If
$ARGUMENTSis empty, tell the subagent: "Review the PR associated with the current branch. Usegh pr view --json number,urlto discover it. If there isn't one, report that back and stop."
After the subagent returns, relay its terse report to the user verbatim (PR URL, counts of findings posted). Do not re-summarize or second-guess the subagent's findings — it already posted the review to GitHub.
$ARGUMENTS
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.
- 11d ago First seen · 13 lines · 0 tokens per session scan A 5334cb4714dd
review-pr is a command published in the GitHub repository criblio/ultra-jira-mcp (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 210 tokens. 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-prs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
code-review
Review code for bugs, improvements, and best practices with actionable feedback.
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.
pn-audit-api
Surgical API design review — REST conventions, status codes, response shapes, validation, and schema leaks. Use standalone or as part of pn-backend-audit. Outputs a scored fix roadmap.
pn-audit-security
OWASP-guided security review — auth posture, input validation, secrets, CORS, JWT, rate limiting. Surgical command for backend security. Use standalone or as part of pn-backend-audit.
review
Review a skill for quality before merge.