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/ci-lane)<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/ci-lane"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-lane/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/ci-lane"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-lane.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.01363 |
| Opus 5 | $0.00006 | $0.00681 |
| Sonnet 5 | $0.00002 | $0.00273 |
| Haiku 4.5 | $0.00001 | $0.00136 |
Grade A, and why
ci-lane 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
kubevirt:ci-lane
Synopsis
/kubevirt:ci-lane <job-name> [--since <period>] [--type <job-type>]
Description
The kubevirt:ci-lane command analyzes recent job runs for a specific CI lane by crawling live Prow data. It provides real-time failure analysis, pattern detection, and comprehensive statistics to help understand job stability and identify problematic tests.
This command uses the healthcheck lane tool to:
- Fetch recent runs for the specified job from Prow
- Parse JUnit test results and build logs
- Identify failure patterns and trends
- Categorize failures by type (infrastructure, test, flaky)
- Provide actionable insights and recommendations
Analysis Capabilities
Failure Pattern Detection
- Groups failures by test name to identify recurring issues
- Calculates failure frequency and rates
- Detects flaky tests (intermittent failures)
- Categorizes by component (migration, storage, compute, network, operator)
Statistics & Metrics
- Total runs analyzed with success/failure breakdown
- Failure rate percentage
- Job type distribution (presubmit, batch, periodic, postsubmit)
- Per-job-type failure rates
- Unique test failure counts
Time-Based Analysis
- Flexible time ranges (hours, days, weeks)
- Automatic pagination to fetch all results in period
- Trend detection (improving, stable, degrading)
- Duration calculations
Implementation
Phase 1: Prerequisites Check
- Verify healthcheck CLI is available:
which healthcheck || echo "healthcheck not found - install from repos/healthcheck" - Validate job name argument provided
Phase 2: Fetch and Analyze Data
- Run healthcheck lane command with summary mode:
healthcheck lane <job-name> --since <period> --summary --output json - Parse JSON output containing:
- Run statistics (total, successful, failed, unknown)
- Failure rate and job type breakdown
- Test failure counts and patterns
- Individual run details with URLs
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 · 156 lines · 12 tokens per session scan A 9b4679d53e1d
ci-lane is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,363 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
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
metrics
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
proxy-logs
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
traces
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
add-debug-wait
Add a wait step to a CI workflow for debugging test failures.
pr-quality-gate-reliability
You are reviewing a pull request for production survivability: how the change behaves when its dependencies misbehave, time out, or fail.