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-search)<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/ci-search"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-search/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-search"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-search.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.00011 | $0.01801 |
| Opus 5 | $0.00005 | $0.00901 |
| Sonnet 5 | $0.00002 | $0.00360 |
| Haiku 4.5 | $0.00001 | $0.00180 |
Grade A, and why
ci-search 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
kubevirt:ci-search
Synopsis
/kubevirt:ci-search <pattern> [--since <period>] [--job <regex>] [--exclude-job <regex>]
Description
The kubevirt:ci-search command searches for specific test failures and error patterns across all KubeVirt CI jobs using the search.ci.kubevirt.io service. It's ideal for investigating recurring failures, understanding failure scope, and finding related issues across different job types.
This command uses the healthcheck search tool to:
- Query the search.ci.kubevirt.io service with regex patterns
- Find matching failures across presubmit, batch, periodic, and postsubmit jobs
- Provide statistics on failure frequency and distribution
- Identify which jobs are most affected
- Generate actionable insights for debugging
Search Capabilities
Pattern Matching
- Regex support for flexible pattern matching
- Search in test names, failure messages, or both
- Case-insensitive matching
- Multiple search types (junit, bug reports, build logs)
Job Filtering
- Filter by job name regex
- Exclude specific jobs or patterns
- Focus on specific job types (periodic, presubmit, batch)
- Target specific SIG areas or Kubernetes versions
Time Range Control
- Default: last 14 days
- Configurable periods (hours, days, weeks)
- Balance between coverage and performance
- Historical trend analysis
Impact Analysis
- Total runs vs matching runs
- Failure rate calculations
- Per-job impact scoring
- Overall CI health metrics
Implementation
Phase 1: Parse Search Parameters
- Extract search pattern (required)
- Parse optional filters:
--since: Time range using human-friendly durations (e.g.,7d,2w,48h). Default: 14 days. Alias for--max-agebut accepts shorthand like7d(days) and2w(weeks) in addition to hours.--job: Job name filter regex--exclude-job: Jobs to exclude--type: Search type (junit, bug, build-log, all)
Phase 2: Execute Search
- Run healthcheck search command:
healthcheck search "<pattern>" --since <period> --job "<regex>" --summary --stats --output json - Parse JSON output containing:
- Total matches across all jobs
- Per-job statistics (runs, failures, matches)
- Test names and failure details
- Job URLs for debugging
- Overall statistics (when --stats is used)
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 · 214 lines · 11 tokens per session scan A 3475abaeeede
ci-search is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,801 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
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…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.