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-list)<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/vep-list"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/vep-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-list"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/vep-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.01128 |
| Opus 5 | $0.00009 | $0.00564 |
| Sonnet 5 | $0.00003 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
vep-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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
kubevirt:vep-list
Synopsis
/kubevirt:vep-list [--sig <sig>] [--release <version>] [--status <status>]
Description
The kubevirt:vep-list command lists KubeVirt Enhancement Proposals (VEPs) from the kubevirt/enhancements repository and the KubeVirt GitHub Projects. It combines data from tracking issues, proposal PRs, and release enhancement tracking projects to provide a comprehensive view.
Data Sources
- kubevirt/enhancements repository: Issues and PRs containing VEP proposals
- KubeVirt Enhancement Tracking Projects: GitHub Projects that track VEPs per release (discovered dynamically via
gh project list --owner kubevirt)
What it Shows
For each VEP, the command displays:
- 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, Tracked, At Risk, Complete, Removed)
- Target Stage: Alpha, Beta, Stable, or Deprecation/Removal
- Promotion Phase: Net New, Remaining, Graduating, or Deprecation
- Assignee: Who is responsible for the VEP
- Release: Which release the VEP is tracked for
Filtering Options
--sig: Filter by SIG (compute, network, storage)--release: Filter by target release (1.8, 1.9, etc.)--status: Filter by tracking status (tracked, at-risk, complete, proposed)
Implementation
-
Fetch Enhancement Projects: List available enhancement tracking projects:
gh project list --owner kubevirt --format json | jq '.projects[] | select(.title | contains("Enhancement"))' -
Fetch Project Items: Get VEPs from the relevant project(s):
gh project item-list <project-number> --owner kubevirt --format json -
Fetch VEP Issues: Get tracking issues from kubevirt/enhancements:
gh issue list --repo kubevirt/enhancements --state open --label kind/enhancement --json number,title,author,assignees,labels,url
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 · 109 lines · 17 tokens per session scan A a9680d2dae36
vep-list is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,128 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.