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/create-eval-from-docs)<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/create-eval-from-docs"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/create-eval-from-docs/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/create-eval-from-docs"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/create-eval-from-docs.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.00012 | $0.01591 |
| Opus 5 | $0.00006 | $0.00796 |
| Sonnet 5 | $0.00002 | $0.00318 |
| Haiku 4.5 | $0.00001 | $0.00159 |
Grade A, and why
create-eval-from-docs 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 10d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
kubevirt:create-eval-from-docs
Synopsis
/kubevirt:create-eval-from-docs <doc-path-or-feature>
Description
The kubevirt:create-eval-from-docs command reads KubeVirt user-guide documentation and generates MCPChecker evaluation tasks for the kubernetes-mcp-server project. It extracts actionable workflows from documentation, maps them to available MCP tools, and produces v1alpha2 task YAML files with setup, prompt, verify, and cleanup phases.
This command bridges the gap between user-facing documentation and automated evaluation coverage. Each generated task validates that an AI agent can complete a real user workflow using the kubernetes-mcp-server's KubeVirt and core toolsets.
Workflow
Input Analysis Generation Output
----- -------- ---------- ------
Doc path/feature --> Read & classify doc --> Map to MCP tools --> Task YAML files
Extract workflows Assess difficulty Verify helpers
Identify prereqs Detect tool gaps Summary report
What It Generates
For each viable workflow found in the documentation:
- A v1alpha2 MCPChecker task YAML file with all four phases (setup, prompt, verify, cleanup)
- New verify helper functions if existing helpers do not cover the workflow
- A summary report with tier classification, MCP tool mapping, and gap analysis
MCP Tool Coverage
The generated tasks test agent use of these MCP tools:
| Toolset | Tools | Use Cases |
|---|---|---|
| kubevirt | vm_create, vm_clone, vm_lifecycle |
VM creation, cloning, start/stop/restart |
| core | resources_create_or_update, resources_get, resources_list, resources_delete |
Any K8s/KubeVirt resource CRUD |
| core | pods_log, pods_exec, events_list |
Debugging, inspection |
| prompts | vm-troubleshoot |
Structured VM diagnostics |
Implementation
Refer to the detailed implementation guide in plugins/kubevirt/skills/create-eval-from-docs/SKILL.md for step-by-step instructions.
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.
- 10d ago First seen · 148 lines · 12 tokens per session scan A 2fdeaf890a88
create-eval-from-docs is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,591 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
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.