list-regressions

list-regressions is a command for Claude Code from wangke19/gemini-ai-helpers. It costs 10 tokens per session (3,112 once invoked), scanned A, original, Apache-2.0.

A command that retrieves unprocessed regression records for an OpenShift release, including test names, timestamps, triage details, and other metadata.

In plain words
What is it for?
Use it to inspect test failures, filter regressions by component or date, and provide data to other analysis commands.
Why use it?
It gives you the underlying records for investigation or custom analysis instead of limiting you to a summary.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 extensions/component-health/skills/list-components/list_components.py --release <release>.

Good fit Use it to inspect test failures, filter regressions by component or date, and provide data to other analysis commands.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers
agentmods
npx agentmods add commands/wangke19/gemini-ai-helpers/list-regressions

Made for: Claude Code.

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.

agentmods badge for list-regressions

README.md
[![agentmods](https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/list-regressions/github.svg)](https://agentmods.dev/commands/wangke19/gemini-ai-helpers/list-regressions)
Your own site
<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/list-regressions"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/list-regressions/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.

agentmods 80×15 button for list-regressions

Your own site · 80×15
<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/list-regressions"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/list-regressions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,112 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.03112
Opus 5 $0.00005 $0.01556
Sonnet 5 $0.00002 $0.00622
Haiku 4.5 $0.00001 $0.00311

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

Security

Grade A, and why

list-regressions 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 9d 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.

extensions/teams/commands/list-regressions.md · 342 lines

How it starts

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

Name

teams:list-regressions

Synopsis

/teams:list-regressions <release> [--components comp1 comp2 ...] [--start YYYY-MM-DD] [--end YYYY-MM-DD]

Description

The teams:list-regressions command fetches regression data for a specified OpenShift release and returns raw regression details without performing any summarization or analysis. It provides complete regression information including test names, timestamps, triages, and metadata.

This command is useful for:

  • Fetching raw regression data for further processing
  • Accessing complete regression details for specific components
  • Building custom analysis workflows
  • Providing data to other commands (like summarize-regressions and analyze)
  • Exporting regression data for offline analysis
  • Investigating specific test failures across releases

Implementation

  1. Verify Prerequisites: Check that Python 3 is installed

    • Run: python3 --version
    • Verify version 3.6 or later is available
  2. Parse Arguments: Extract release version and optional filters from arguments

    • Release format: "X.Y" (e.g., "4.17", "4.21")
    • Optional filters:
      • --components: Space-separated list of component search strings (fuzzy match)
      • --start: Start date for filtering (YYYY-MM-DD)
      • --end: End date for filtering (YYYY-MM-DD)
      • --short: Exclude regression arrays from output (only summaries)
  3. Resolve Component Names: Use fuzzy matching to find actual component names

    • Run list_components.py to get all available components:
      python3 extensions/component-health/skills/list-components/list_components.py --release <release>
      
    • If --components was provided:
      • For each search string, find all components containing that string (case-insensitive)
      • Example: "network" matches "Networking / ovn-kubernetes", "Networking / DNS", etc.
      • Combine all matches into a single list
      • Remove duplicates
      • If no matches found for a search string, warn the user and show available components
    • If --components was NOT provided:
      • Use all available components from the list

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

  1. 9d ago First seen · 342 lines · 10 tokens per session scan A f858bf84f5e3

Subscribe to this mod's changes

list-regressions is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 3,112 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-09-03.