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-review-list)<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/vep-review-list"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/vep-review-list/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-review-list"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/vep-review-list.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.00017 | $0.01937 |
| Opus 5 | $0.00009 | $0.00968 |
| Sonnet 5 | $0.00003 | $0.00387 |
| Haiku 4.5 | $0.00002 | $0.00194 |
Grade A, and why
vep-review-list 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
kubevirt:vep-review-list
Synopsis
/kubevirt:vep-review-list [username] [--release <version>]
Description
The kubevirt:vep-review-list command lists all VEPs where a user is assigned as a VEP Reviewer on the KubeVirt Enhancement Tracking project board, along with their associated proposal and implementation PRs. Only open PRs are shown — merged and closed PRs are filtered out so the reviewer can focus on what still needs attention.
If no username is provided, the command defaults to the current user's GitHub handle (via gh api user).
Data Sources
- KubeVirt Enhancement Tracking Projects: GitHub Projects (discovered dynamically) that track VEPs per release. The project board contains custom fields including "VEP reviewer", "VEP approver", "Proposal PRs", "Impl PRs", "SIG", "Status", "Target Stage", and "Promotion Phase"
- kubevirt/enhancements repository: For checking PR state of proposal PRs
- kubevirt/kubevirt repository: For checking PR state of implementation PRs
What it Shows
For each VEP assigned to the reviewer:
- VEP Number: The VEP identifier (e.g., VEP 190)
- Title: Brief description of the enhancement
- SIG: The owning SIG (compute, network, storage)
- Status: From project tracking (Proposed for consideration, Tracked, At Risk, Complete, Removed from Milestone)
- Target Stage: Alpha, Beta, Stable, or Deprecation/Removal
- Promotion Phase: Net New, Remaining, Graduating, or Deprecation
- Assignee: The VEP author/owner
- Proposal PRs: Open VEP PRs in kubevirt/enhancements (merged/closed filtered out)
- Implementation PRs: Open code PRs in kubevirt/kubevirt (merged/closed filtered out)
Implementation
-
Resolve GitHub Username: Determine the reviewer's GitHub handle:
# If no username argument provided, get the current user gh api user --jq '.login' -
Discover Enhancement Projects: List available enhancement tracking projects:
gh project list --owner kubevirt --format json | jq '.projects[] | select(.title | contains("Enhancement"))'If
--releaseis specified, match the project title containing that release version (e.g., "KubeVirt 1.9 Enhancements Tracking"). Otherwise, search all non-template enhancement tracking projects. Skip template projects (titles starting with "[TEMPLATE]").
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 · 189 lines · 17 tokens per session scan A 985eced380b5
vep-review-list is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 10d ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,937 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.