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.
npx skills add wangke19/gemini-ai-helpers --skill fetch-regression-detailsgit clone --depth 1 https://github.com/wangke19/gemini-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/skills/wangke19/gemini-ai-helpers/fetch-regression-details)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/fetch-regression-details"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-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.
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/fetch-regression-details"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/fetch-regression-details.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.00018 | $0.03791 |
| Opus 5 | $0.00009 | $0.01895 |
| Sonnet 5 | $0.00004 | $0.00758 |
| Haiku 4.5 | $0.00002 | $0.00379 |
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 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.
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` How it starts
The opening of the file, as written. The whole thing — 429 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
-
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
- Check:
-
Python 3: Python 3.6 or later
- Check:
python3 --version - Should be available on most systems
- Uses only standard library (no external dependencies)
- Check:
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="extensions/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')
What ships with it
2 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.
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 · 429 lines · 18 tokens per session scan A 64bdc0e24143
Fetch Regression Details is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 3,791 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
gcloud-usage
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
spk-admin-setup-doctor
Install, verify, and repair Spec Kitty commands, skills, agent paths, runtime prerequisites, and common setup failures.
lov-fix-deepseek-tool-call-error
A recovery and investigation tool for a Codex conversation using DeepSeek, an AI service, when a failed tool request returns “No tool output found for tool call.” It examines local session records and reports how to resume the work.
lov-fix-by-add-log
A debugging assistant that adds a small amount of targeted diagnostic logging and uses the resulting output to investigate a hard-to-reproduce problem.
lov-fix-general
A software troubleshooting workflow for finding the cause of an error, applying a focused fix, and checking the original failing path again.
lov-fix-until-no-error
A verification-focused debugging workflow that repeatedly runs specified checks, fixes the highest-priority failure, and stops when the checks pass or a genuine external blockage remains.