Triage Regression

Triage Regression is a skill for Claude Code, Codex from wangke19/gemini-ai-helpers. It costs 22 tokens per session (2,696 once invoked), scanned A, a copy of triage-regression, Apache-2.0.

A procedure for creating or updating a Component Readiness triage record through the Sippy API and linking regressions to a JIRA bug. A regression is a previously working behavior that has become unreliable or broken.

In plain words
What is it for?
Use it to triage one or more Component Readiness regressions, using a JIRA URL and a triage type such as product, test, or CI infrastructure.
Why use it?
It keeps related failures connected to the bug responsible for investigating them and supports adding more regressions later.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to triage one or more Component Readiness regressions, using a JIRA URL and a triage type such as product, test, or CI infrastructure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wangke19/gemini-ai-helpers/triage-regression
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 wangke19/gemini-ai-helpers --skill triage-regression
Clone the repo
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers

Made for: Claude Code, Codex.

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 Triage Regression

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/triage-regression"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/triage-regression.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,696 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 100% copy Near-identical to another mod 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.00022 $0.02696
Opus 5 $0.00011 $0.01348
Sonnet 5 $0.00004 $0.00539
Haiku 4.5 $0.00002 $0.00270

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

Security

Grade A, and why

Triage Regression 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 12d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (triage_regression.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.

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.

Origin

This is a copy

100% identical to triage-regression — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

extensions/ci/skills/triage-regression/SKILL.md · 318 lines

How it starts

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

Triage Regression

This skill creates or updates triage records via the Sippy API, linking one or more Component Readiness regressions to a JIRA bug.

When to Use This Skill

Use this skill when you need to:

  • File a triage record for one or more regressions identified by the analyze-regression command
  • Link multiple related regressions to a single JIRA bug
  • Update an existing triage to add more regressions or change details

Prerequisites

  1. OpenShift CLI Authentication: Required for authenticating to the sippy-auth API

    • Must be logged into the DPCR cluster via oc login
    • Cluster API: https://api.cr.j7t7.p1.openshiftapps.com:6443
    • Use the oc-auth skill to obtain the Bearer token
  2. Python 3: Python 3.6 or later

    • Check: python3 --version
    • Uses only standard library (no external dependencies)
  3. Input Data: Requires regression IDs, a JIRA bug URL, and a triage type

    • Regression IDs: from Component Readiness UI or fetch-regression-details skill
    • JIRA URL: an existing JIRA bug (e.g., https://redhat.atlassian.net/browse/OCPBUGS-12345)
    • Triage type: product, test, ci-infra, or product-infra

Implementation Steps

Step 1: Obtain Authentication Token

Use the oc-auth skill to obtain a Bearer token from the DPCR cluster:

# Get token from the DPCR cluster context
# The oc-auth skill's curl_with_token.sh uses this cluster for sippy-auth
DPCR_CLUSTER="https://api.cr.j7t7.p1.openshiftapps.com:6443"

# Find the oc context for the DPCR cluster and get the token
CONTEXT=$(oc config get-contexts -o name 2>/dev/null | while read -r ctx; do
  server=$(oc config view -o jsonpath="{.clusters[?(@.name=='$(oc config view -o jsonpath="{.contexts[?(@.name=='$ctx')].context.cluster}" 2>/dev/null)')].cluster.server}" 2>/dev/null || echo "")
  server_clean=$(echo "$server" | sed -E 's|^https?://||')
  if [ "$server_clean" = "api.cr.j7t7.p1.openshiftapps.com:6443" ]; then
    echo "$ctx"
    break
  fi
done)

if [ -z "$CONTEXT" ]; then
  echo "Error: Not logged into DPCR cluster. Please run: oc login $DPCR_CLUSTER"
  exit 1
fi

TOKEN=$(oc whoami -t --context="$CONTEXT" 2>/dev/null)
if [ -z "$TOKEN" ]; then
  echo "Error: Failed to get token. Please re-authenticate to DPCR cluster."
  exit 1
fi

Read the full file on GitHub · 318 lines

Files

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.

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. 12d ago First seen · 318 lines · 22 tokens per session scan A 2f116481a7cf

Subscribe to this mod's changes

Triage Regression is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 2,696 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to triage-regression, differing in 12 lines, and is treated as a copy.