vep-find-reviewers

vep-find-reviewers is a skill for Claude Code from lyarwood/kubevirt-ai-helpers. It costs 50 tokens per session (2,542 once invoked), scanned A, original, Apache-2.0.

A guide for finding suitable reviewers for a KubeVirt Enhancement Proposal, or VEP, which is a documented proposal for a KubeVirt project change. It uses ownership files and past Git contributions to identify people familiar with the relevant code.

In plain words
What is it for?
Use it with a VEP number or SIG, a KubeVirt special-interest group, to identify candidate reviewers from ownership records and commit history.
Why use it?
It helps proposal authors choose reviewers based on project responsibility and prior work instead of guessing. It requires access to GitHub data.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the kubevirt plugin — 4 skills, 17 commands shipped together

Good fit Use it with a VEP number or SIG, a KubeVirt special-interest group, to identify candidate reviewers from ownership records and commit history.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lyarwood/kubevirt-ai-helpers/vep-find-reviewers
Install

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.

Any agent
npx skills add lyarwood/kubevirt-ai-helpers --skill vep-find-reviewers
Clone the repo
git clone --depth 1 https://github.com/lyarwood/kubevirt-ai-helpers

Made for: Claude Code.

Or install kubevirt, the plugin that ships this one along with the rest of its 4 skills, 17 commands.

Wrote 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.

agentmods badge for vep-find-reviewers

README.md
[![agentmods](https://agentmods.dev/badge/skills/lyarwood/kubevirt-ai-helpers/vep-find-reviewers/github.svg)](https://agentmods.dev/skills/lyarwood/kubevirt-ai-helpers/vep-find-reviewers)
Your own site
<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.

agentmods 80×15 button for vep-find-reviewers

Your own site · 80×15
<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>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,542 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.02542
Opus 5 $0.00025 $0.01271
Sonnet 5 $0.00010 $0.00508
Haiku 4.5 $0.00005 $0.00254

Measured 12d ago against content hash 33621f86f78a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

plugins/kubevirt/skills/vep-find-reviewers/SKILL.md · 268 lines

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-reviewers command
  • 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

  1. gh CLI: Must be installed and authenticated (gh auth status)
  2. 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):

  1. Discover enhancement tracking projects:

    gh project list --owner kubevirt --format json | jq '.projects[] | select(.title | contains("Enhancement")) | select(.title | startswith("[TEMPLATE]") | not)'
    
  2. 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.

Read the full file on GitHub · 268 lines

Changes

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.

  1. 12d ago First seen · 268 lines · 50 tokens per session scan A 33621f86f78a

Subscribe to this mod's changes

vep-find-reviewers is a skill published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,542 once invoked, about $0.0003 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.