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/lyarwood/kubevirt-ai-helpersWrote 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/lyarwood/kubevirt-ai-helpers/review-pr)<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/review-pr"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/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/lyarwood/kubevirt-ai-helpers/review-pr"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/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.00016 | $0.01971 |
| Opus 5 | $0.00008 | $0.00986 |
| Sonnet 5 | $0.00003 | $0.00394 |
| Haiku 4.5 | $0.00002 | $0.00197 |
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 12d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
kubevirt:review-pr
Synopsis
/kubevirt:review-pr <pr-number-or-url>
Description
The kubevirt:review-pr command performs a comprehensive code review of a GitHub pull request using the gh CLI, applying KubeVirt project coding conventions and reviewer guidelines. Unlike /kubevirt:review (which reviews local branch changes), this command works directly against a remote PR without requiring a local checkout.
This command simulates a thorough code review following the KubeVirt multi-pass review approach. Read the shared review checklist at plugins/kubevirt/skills/review/SKILL.md for the full list of review areas, conventions, and output formatting rules.
Review Passes
- PR Metadata Pass: Evaluate PR title, description, labels, and overall scope
- General Design Pass: Verify the overall design makes sense and code structure is consistent with the project
- Detailed Code Pass: In-depth analysis of the implementation via the diff
- Standards Compliance Pass: Check adherence to KubeVirt coding conventions
- Commit History Pass: Review commit structure and messages
Implementation
Phase 1: Gather PR Metadata
- Parse the PR argument to extract the PR number and repository (defaults to
kubevirt/kubevirt) - Use
gh pr view <pr-number> --repo <repo> --json number,title,body,labels,author,reviewRequests,assignees,baseRefName,headRefName,additions,deletions,changedFiles,commits,comments,reviews,state,isDraftto get full PR metadata - Evaluate PR title, description, size, and draft status using the PR Metadata checklist from the shared review skill
- Flag PRs that are too large (>500 lines changed across many files) and suggest splitting
Phase 2: Fetch PR Diff and Changed Files
- Use
gh pr diff <pr-number> --repo <repo>to get the full diff - Use
gh pr view <pr-number> --repo <repo> --json filesto get the list of changed files with per-file stats - Prioritize files for review using the file priority order from the shared review checklist
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.
- 12d ago First seen · 140 lines · 16 tokens per session scan A 090fb5781059
review-pr is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,971 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 commands, from other repositories
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
code-review
Code review for branch changes. Analyzes git diff between branches with multi-level depth (low/medium/high). Matches changes against task description. Returns structured report with severity levels and verdict.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.