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-report)<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/ci-report"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-report/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-report"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-report.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.00007 | $0.02071 |
| Opus 5 | $0.00003 | $0.01035 |
| Sonnet 5 | $0.00001 | $0.00414 |
| Haiku 4.5 | $0.00001 | $0.00207 |
Grade A, and why
ci-report 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 11d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
kubevirt:ci-report
Synopsis
/kubevirt:ci-report [--scope <scope>] [--format <format>] [--recipient <audience>]
Description
The kubevirt:ci-report command generates comprehensive CI health reports optimized for different stakeholders and purposes. It consolidates data from multiple sources to provide executive summaries, detailed analyses, and actionable insights for CI/CD pipeline health management.
This command leverages healthcheck MCP tools to:
- Aggregate CI health data across all relevant jobs
- Generate trend analysis and health metrics
- Identify critical issues and recommendations
- Format reports for different audiences (executives, engineers, release managers)
- Provide actionable next steps with prioritization
Report Capabilities
Multiple Formats
- Summary: Concise overview with key metrics (1-2 pages)
- Detailed: Comprehensive analysis with all findings (5-10 pages)
- Executive: High-level status for leadership (1 page)
- Release: Pre-release health assessment (3-5 pages)
Flexible Scopes
- Daily: Last 24 hours of CI activity
- Weekly: 7-day rolling health report
- Release: Health assessment for upcoming release
- Custom Job: Focus on specific job or category
Stakeholder Optimization
- Engineering teams: Technical details, root causes, debug links
- Management: Executive summaries, trend indicators, resource needs
- Release managers: Blocking issues, risk assessment, go/no-go recommendations
- SRE teams: Infrastructure issues, capacity problems, monitoring gaps
Report Sections
Executive Summary
- Overall CI health status (healthy, unstable, unhealthy, critical)
- Key metrics dashboard (failure rates, test counts, job stability)
- Top 3 priority issues requiring attention
- Trend indicator (improving, stable, degrading)
- Recommended actions and resource allocation
Health Metrics
- Total jobs monitored
- Overall pass/fail rates
- Failure rate trends (vs previous period)
- Quarantine effectiveness
- Infrastructure issue counts
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.
- 11d ago First seen · 275 lines · 7 tokens per session scan A 9c6ec933530b
ci-report is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 7 tokens to every session and 2,071 once invoked, about $0.0000 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
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
ADO: Get Build Info
Query Azure DevOps build pipeline status and failure details, optionally linking results to work items.