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.
npx skills add lyarwood/kubevirt-ai-helpers --skill vep-find-reviewersgit 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/skills/lyarwood/kubevirt-ai-helpers/vep-find-reviewers)<a href="https://agentmods.dev/skills/lyarwood/kubevirt-ai-helpers/vep-find-reviewers"><img src="https://agentmods.dev/badge/skills/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/skills/lyarwood/kubevirt-ai-helpers/vep-find-reviewers"><img src="https://agentmods.dev/badge/skills/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.00050 | $0.02542 |
| Opus 5.5 | $0.00020 | $0.01017 |
| Sonnet 5.5 | $0.00010 | $0.00508 |
| Haiku 4.5 | $0.00005 | $0.00254 |
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 1mo 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VEP Find Reviewers
This skill provides the detailed implementation logic for the /kubevirt:vep-find-reviewers command. It covers how to parse OWNERS_ALIASES files, map SIGs to code directories, and analyze git history to identify active contributors.
When to Use This Skill
- When executing the
/kubevirt:vep-find-reviewerscommand - When a user asks who should review a VEP or implementation PR
- When a VEP author needs help finding domain experts for their proposal
Prerequisites
- gh CLI: Must be installed and authenticated (
gh auth status) - Network access: Requires access to the GitHub API for fetching file contents and commit history
Implementation Steps
Step 1: Resolve the Input
Determine whether the user provided a VEP number or a SIG name.
If numeric (VEP number):
-
Discover enhancement tracking projects:
gh project list --owner kubevirt --format json | jq '.projects[] | select(.title | contains("Enhancement")) | select(.title | startswith("[TEMPLATE]") | not)' -
Search each project for the VEP using GraphQL to get the SIG field:
gh api graphql -f query=' { organization(login: "kubevirt") { projectV2(number: <project-number>) { items(first: 100) { nodes { content { ... on Issue { number title } } fieldValues(first: 30) { nodes { ... on ProjectV2ItemFieldSingleSelectValue { name field { ... on ProjectV2SingleSelectField { name } } } ... on ProjectV2ItemFieldTextValue { text field { ... on ProjectV2Field { name } } } } } } } } } }'Match the item whose issue number equals the VEP number. Extract the "SIG" field value.
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.
- 1mo ago First seen · 268 lines · 50 tokens per session scan A 33621f86f78a
vep-find-reviewers is a skill published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,542 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…