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/vep-find-reviewers)<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/vep-find-reviewers"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/vep-find-reviewers/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/vep-find-reviewers"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/vep-find-reviewers.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.00015 | $0.01781 |
| Opus 5 | $0.00008 | $0.00890 |
| Sonnet 5 | $0.00003 | $0.00356 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
vep-find-reviewers 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
kubevirt:vep-find-reviewers
Synopsis
/kubevirt:vep-find-reviewers <vep-number-or-sig> [--repo <repo>] [--months <n>]
Description
The kubevirt:vep-find-reviewers command identifies potential reviewers for a KubeVirt Enhancement Proposal (VEP) by combining two sources:
- OWNERS_ALIASES: SIG-based reviewer and approver lists from the kubevirt/kubevirt repository
- Recent git activity: Contributors who have recently modified code in areas relevant to the VEP
This helps VEP authors and SIG leads find the right people to review a proposal or its implementation PRs, especially when the VEP spans multiple areas or when the OWNERS_ALIASES lists are stale.
Input Modes
- VEP number: Looks up the VEP's SIG from the enhancement tracking project, then finds reviewers for that SIG. If the VEP proposal names specific packages or directories, those are used to scope the git history search.
- SIG name: Directly looks up reviewers for the given SIG (e.g.,
compute,network,storage).
What it Shows
For each candidate reviewer:
- Username: GitHub handle
- Source: How they were identified (OWNERS_ALIASES, git activity, or both)
- Role: Reviewer or approver (from OWNERS_ALIASES)
- Recent activity: Number of commits and PRs merged in the relevant area within the lookback window
- Last active: Date of most recent merge in the area
Skill Reference
This command uses the vep-find-reviewers skill for detailed implementation guidance on parsing OWNERS_ALIASES files and analyzing git history. See plugins/kubevirt/skills/vep-find-reviewers/SKILL.md.
Implementation
-
Resolve Input: Determine whether the argument is a VEP number or SIG name:
- If numeric, fetch the VEP from the enhancement tracking project to get its SIG and identify affected code areas from the VEP proposal content
- If a SIG name (compute, network, storage), use it directly
-
Fetch OWNERS_ALIASES: Retrieve the OWNERS_ALIASES file from kubevirt/kubevirt:
gh api repos/kubevirt/kubevirt/contents/OWNERS_ALIASES --jq '.content' | base64 -dParse the YAML to extract members of relevant aliases (e.g.,
sig-compute-reviewers,sig-compute-approvers). See thevep-find-reviewersskill for the full alias naming conventions and parsing details.
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 · 154 lines · 15 tokens per session scan A 6a551867493f
vep-find-reviewers is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 10d ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,781 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.