Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/wangke19/gemini-ai-helpers/hcp-create-kubevirt)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/hcp-create-kubevirt"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/hcp-create-kubevirt/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/wangke19/gemini-ai-helpers/hcp-create-kubevirt"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/hcp-create-kubevirt.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.00027 | $0.04681 |
| Opus 5 | $0.00014 | $0.02341 |
| Sonnet 5 | $0.00005 | $0.00936 |
| Haiku 4.5 | $0.00003 | $0.00468 |
Grade A, and why
HyperShift KubeVirt Provider 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 8d 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.
This is a copy
94% identical to hcp-create-kubevirt — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 595 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HyperShift KubeVirt Provider
This skill provides implementation guidance for creating HyperShift clusters using the KubeVirt provider, which runs on existing Kubernetes clusters with special attention to network conflict prevention and virtual machine management.
When to Use This Skill
This skill is automatically invoked by the /hcp:generate kubevirt command to guide the KubeVirt provider cluster creation process.
Prerequisites
- Kubernetes cluster with KubeVirt installed and configured
- Sufficient compute resources on the host cluster
- Storage classes configured for VM disks
- HyperShift operator installed
- Pull secret for accessing OpenShift images
KubeVirt Provider Overview
KubeVirt Provider Peculiarities
- Runs on existing Kubernetes cluster: Host cluster provides compute resources
- CRITICAL Network Isolation: Management cluster network cannot conflict with HostedCluster network
- Storage Requirements: Requires storage classes for VM disks and persistent volumes
- Virtual Machine Templates: Uses VM-based nodes instead of bare metal
- IPv6 Support: Full IPv6 support available
- Disconnected Capable: Can run in airgapped environments
- Resource Planning: Requires sufficient compute resources on host cluster
Network Conflict Prevention (CRITICAL)
The most important aspect of KubeVirt clusters is preventing network conflicts:
- Service/Cluster/Machine CIDRs must not overlap with management cluster
- Default CIDRs are designed to avoid common management cluster ranges
- Always check management cluster CIDRs before setting HostedCluster CIDRs
Common management cluster ranges to avoid:
- 10.128.0.0/14 (common OCP default)
- 10.0.0.0/16 (common private range)
- 192.168.0.0/16 (common private range)
Implementation Steps
Step 1: Analyze Cluster Description
Parse the natural language description for KubeVirt-specific requirements:
Environment Type Detection:
- Development: "dev", "development", "testing", "lab", "demo"
- Production: "prod", "production", "critical", "enterprise"
- Disconnected: "airgapped", "disconnected", "offline", "air-gapped"
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.
- 8d ago First seen · 595 lines · 27 tokens per session scan A 451f82bbfa0a
HyperShift KubeVirt Provider is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 4,681 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to hcp-create-kubevirt, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.
vmware-vks
Use this skill whenever the user needs to manage vSphere Kubernetes Service (VKS) — Supervisor clusters, vSphere Namespaces, and TKC cluster lifecycle. Directly handles: check VKS compatibility, create/delete namespaces, create/scale/upgrade/delete TKC clusters, get kubeconfig, check Harbor registry. Always use this…
platform-build
Platform Developer: Stage 4 build task. Docker Compose setup, infra config, PR summary authoring, and Stage 4 gate writing for the platform workstream.
containerize
Build a minimal non-root OCI image for a uv-managed Python app with a pinned multi-stage Dockerfile, then scan, sign, and attest it. Use when containerizing Python.
trivy
Run Trivy scans for dependency vulnerabilities, IaC misconfigurations, secrets, licenses, SBOMs, and container images with the shared trivy.yaml. Use for any trivy command.