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-enhancement)<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/review-enhancement"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/review-enhancement/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-enhancement"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/review-enhancement.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.00024 | $0.03077 |
| Opus 5 | $0.00012 | $0.01538 |
| Sonnet 5 | $0.00005 | $0.00615 |
| Haiku 4.5 | $0.00002 | $0.00308 |
Grade A, and why
review-enhancement 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
kubevirt:review-enhancement
Synopsis
/kubevirt:review-enhancement <pr-number-or-url | vep-number>
Description
The kubevirt:review-enhancement command performs a comprehensive review of a KubeVirt Enhancement Proposal (VEP) combining process compliance checks with a multi-pass technical content review. The primary input is an enhancements PR (number or URL); the command resolves the VEP it touches, the tracking issue, project board data, and implementation PRs, then evaluates the enhancement from both a process and technical reviewer perspective. A VEP number is also accepted and disambiguated automatically.
All process and technical checks are grounded in the best practices codified in the kubevirt/enhancements repository itself, which the command reads live at review time (rather than relying on a hard-coded snapshot):
README.md-- the VEP process, responsibilities, labels, deadlines, and exceptionsdocs/feature-lifecycle.md-- feature gates, graduation phases, and the release stage transition tableveps/NNNN-vep-template/vep.md-- required sections.github/PULL_REQUEST_TEMPLATE.md-- the expected PR metadata
The command distinguishes between two kinds of PR:
- New VEP (the PR adds a new
veps/sig-*/NNNN-*/vep.md): reviewed for completeness, design quality, and process compliance. - Update to an existing VEP (the PR modifies an existing
vep.md, e.g. a graduation or design change): in addition to the above, the command reviews the existing implementation code and PRs to verify the VEP is still accurate -- that the proposal has not diverged from what was actually built, and that any stage bump (Alpha -> Beta -> GA) is backed by merged implementation as required by the feature lifecycle.
This command uses the review-enhancement skill for detailed implementation guidance. See plugins/kubevirt/skills/review-enhancement/SKILL.md.
Data Sources
- Enhancements PR: The VEP proposal/update PR under review in kubevirt/enhancements
- Best-Practice Docs (read live):
README.md,docs/feature-lifecycle.md, the VEP template, and the PR template from kubevirt/enhancements - Tracking Issue: VEP tracking issue in kubevirt/enhancements
- GitHub Projects: Enhancement tracking projects for release planning
- Implementation PRs and Code: Code PRs and merged implementation in kubevirt/kubevirt and other repos (used to verify accuracy of VEP updates)
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 Changed · +25 lines · +11 tokens per session 0e0475a99002
- 12d ago First seen · 253 lines · 13 tokens per session scan A 888cc354d3e2
review-enhancement is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 10d ago), licensed Apache-2.0. It adds 24 tokens to every session and 3,077 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.