fetch-regression-details

fetch-regression-details is a skill for Claude Code from openshift-eng/ai-helpers. It costs 19 tokens per session (4,984 once invoked), scanned A, original, Apache-2.0.

A tool that retrieves detailed information about a Component Readiness regression from the Sippy API. Component Readiness is an OpenShift view of how reliably components and tests work across releases.

In plain words
What is it for?
Use it to analyze a specific regression, check existing bug assignments, or create an evidence-based regression report.
Why use it?
It puts the regression's test, release, affected variants, triage state, and sample failed jobs together for investigation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ci plugin — 35 skills, 21 commands, 2 agents shipped together

Good fit Use it to analyze a specific regression, check existing bug assignments, or create an evidence-based regression report.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openshift-eng/ai-helpers/fetch-regression-details
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.

Any agent
npx skills add openshift-eng/ai-helpers --skill fetch-regression-details
Clone the repo
git clone --depth 1 https://github.com/openshift-eng/ai-helpers

Made for: Claude Code.

Or install ci, the plugin that ships this one along with the rest of its 35 skills, 21 commands, 2 agents.

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 fetch-regression-details

README.md
[![agentmods](https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/fetch-regression-details/github.svg)](https://agentmods.dev/skills/openshift-eng/ai-helpers/fetch-regression-details)
Your own site
<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/fetch-regression-details"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/fetch-regression-details/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 fetch-regression-details

Your own site · 80×15
<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/fetch-regression-details"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/fetch-regression-details.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,984 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00019 $0.04984
Opus 5.5 $0.00008 $0.01994
Sonnet 5.5 $0.00004 $0.00997
Haiku 4.5 $0.00002 $0.00498

Measured 22d ago against content hash 439bd250d8bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fetch-regression-details scanned grade A with 1 finding 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 22d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (fetch_regression_details.py, test_fetch_regression_details.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Check: `curl -s https://sippy.dptools.openshift.org/api/health`
plugins/ci/skills/fetch-regression-details/SKILL.md · 475 lines

How it starts

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

Fetch Regression Details

This skill fetches detailed regression information from the Component Readiness API. It retrieves comprehensive data about a specific regression including test name, affected variants, release information, triage status, and related metadata.

When to Use This Skill

Use this skill when you need to retrieve complete details about a Component Readiness regression, such as:

  • Analyzing a specific regression from Component Readiness
  • Getting test name, release, and variant information for a regression
  • Checking triage status and existing bug assignments
  • Building regression analysis reports
  • Automating regression workflows

Prerequisites

  1. Network Access: Must be able to reach the Sippy API

    • Check: curl -s https://sippy.dptools.openshift.org/api/health
    • No authentication required for public API endpoints
  2. Python 3: Python 3.6 or later

    • Check: python3 --version
    • Should be available on most systems
    • Uses only standard library (no external dependencies)

Implementation Steps

Step 1: Run the Python Script

The skill uses a Python script to fetch and parse regression data (including sample failed jobs):

# Path to the Python script
script_path="plugins/ci/skills/fetch-regression-details/fetch_regression_details.py"

# Fetch regression data in JSON format (includes failed jobs)
python3 "$script_path" <regression_id> --format json

# Or fetch as human-readable summary
python3 "$script_path" <regression_id> --format summary

Step 2: Parse the Output

The script outputs structured JSON data that can be further processed:

# Store JSON output in a variable for processing
regression_data=$(python3 "$script_path" 34446 --format json)

# Extract specific fields using jq if needed
test_name=$(echo "$regression_data" | jq -r '.test_name')
component=$(echo "$regression_data" | jq -r '.component')
jira_keys=$(echo "$regression_data" | jq -r '.triages[].jira_key')

# Extract failed job URLs for analysis
failed_job_urls=$(echo "$regression_data" | jq -r '.sample_failed_jobs | to_entries[] | .value.failed_runs[] | .job_url')

Read the full file on GitHub · 475 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 22d ago Changed · +1 lines 439bd250d8bb
  2. 1mo ago Changed 09603fa006a8
  3. 1mo ago First seen · 474 lines · 19 tokens per session scan A 993c3986a65f

Subscribe to this mod's changes

fetch-regression-details is a skill published in the GitHub repository openshift-eng/ai-helpers (119 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 4,984 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens