A command-line report of the health of a project's continuous integration (CI), the automated checks that run on code changes. It reviews recent merge-time jobs and groups their failures by area, branch, and test.

Use it to inspect recent CI failures, rank tests that fail most often, find problems shared across jobs, compare categories or release branches, and choose CI maintenance work.

It helps find recurring or widespread test failures without manually inspecting every CI job. It also shows which tests are quarantined, meaning temporarily excluded from blocking changes, and whether that quarantine is helping.

ci-health — Command for Claude Code by lyarwood

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.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-health/github.svg)](https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/ci-health)

Your own site

<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/ci-health"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-health/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/ci-health"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,487 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.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.01487
Opus 5	$0.00005	$0.00744
Sonnet 5	$0.00002	$0.00297
Haiku 4.5	$0.00001	$0.00149

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

Security

Grade A, and why

ci-health 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/commands/ci-health.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Name

kubevirt:ci-health

Synopsis

/kubevirt:ci-health [category] [--since <period>]

Description

The kubevirt:ci-health command provides a quick overview of CI health across all merge-time jobs using pre-aggregated data from the kubevirt/ci-health project. It identifies trending failures, highlights quarantined tests, and helps prioritize CI maintenance work.

This command uses the healthcheck merge tool to:

Fetch aggregated failure data from ci-health API
Filter by job category (compute, network, storage, operator, release)
Count and rank test failures across jobs
Identify quarantined tests and their effectiveness
Detect failure patterns and trends

Key Capabilities

Fast Aggregated Analysis

Uses pre-computed ci-health data for speed
Covers all merge-time jobs (main, release branches)
No heavy Prow crawling required
Limited to recent data (typically last 48 hours)

Failure Categorization

Group by SIG area (compute, network, storage, operator)
Filter by release branch (main, 1.6, 1.5, 1.4)
Identify cross-job failures
Detect systematic issues

Quarantine Intelligence

Highlight quarantined tests
Assess quarantine effectiveness
Identify candidates for quarantine removal
Track quarantine staleness

Implementation

Phase 1: Parse Arguments

Determine category filter (default: all jobs)
- Aliases: compute, network, storage, operator, main, 1.6, 1.5, 1.4
- Custom regex patterns supported
Parse time period (default: all available ci-health data)

Phase 2: Fetch CI Health Data

Run healthcheck merge command:

healthcheck merge <category> --count --quarantine --output json

Parse JSON output containing:
- Test failure counts grouped by test name
- Failed job URLs
- Quarantine status
- Failure details with context

Phase 3: Analyze Patterns

Rank failures by frequency
- Sort tests by occurrence count
- Identify top 10 most frequent failures
- Calculate failure distribution

Read the full file on GitHub · 190 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.

12d ago First seen · 190 lines · 11 tokens per session scan A 8152424adb01

Subscribe to this mod's changes

ci-health is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 10d ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,487 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.

Analytics and metrics CI and CD DevOps and cloud

ci-health