What is analyze-disruption?

A troubleshooting tool for disruption in Prow CI runs, where Prow is a system that runs tests automatically. It examines timelines, audit records, pod logs, and CPU data to compare runs and find likely causes.

Use it with Prow job links or a Grafana disruption dashboard to compare runs, trace disruption across backends, and investigate root causes.

It brings several kinds of test-run evidence together, so you do not have to inspect logs and metrics separately when investigating interruptions.

analyze-disruption — Skill for Claude Code by openshift-eng

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 analyze-disruption

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 34 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/analyze-disruption.svg)](https://agentmods.dev/skills/openshift-eng/ai-helpers/analyze-disruption)

Your own site

<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/analyze-disruption"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/analyze-disruption.svg" alt="Measured on agentmods" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 9,536 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. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00032	$0.09536
Opus 5	$0.00016	$0.04768
Sonnet 5	$0.00006	$0.01907
Haiku 4.5	$0.00003	$0.00954

Measured 8d ago against content hash 7761936efbb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

analyze-disruption 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 8d ago.

The scan reads SKILL.md. This mod also ships 6 executable files (download_timelines.py, find_disruption_runs.py, parse_disruption.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.

plugins/ci/skills/analyze-disruption/SKILL.md · 777 lines

How it starts

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

Analyze Disruption

This skill analyzes disruption events recorded in Prow CI job runs. It downloads interval/timeline data, audit logs, and pod logs, then correlates disruption across backends and job runs to identify root causes.

Prerequisites

gcloud CLI Installation
- Check if installed: which gcloud
- The test-platform-results bucket is publicly accessible — no authentication required
Python 3 (3.7 or later)

Input Format

The user will provide one of the following as input:

Option A — Prow job URLs (direct analysis):

One or more Prow job URLs (at least 1)
- Example: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn/1983307151598161920

Option B — Grafana disruption dashboard URL (run discovery + analysis):

A Grafana disruption dashboard URL — the skill extracts filter parameters, finds matching job runs via Sippy, and presents candidates for the user to select before analysis
- Example: https://grafana-loki.ci.openshift.org/d/gEdw_aLvk/disruption-for-5-0-os-agnostic?var-platform=gcp&var-backend=host-to-host-new-connections&var-upgrade_type=micro&var-architectures=amd64&var-topologies=ha&var-networks=ovn&var-releases=5.0
- Recognized by hostname grafana-loki.ci.openshift.org and path starting with /d/
- The var-backend value automatically sets the --backends filter unless overridden

Optional flags (both input options):

--backends flag (optional) — comma-separated list of backend names to focus on
- Example: --backends kube-api,oauth-api,openshift-api
- If omitted, analyze all backends that show disruption (Option A) or use the Grafana var-backend value (Option B)
--skip-jira flag (optional) — skip the Jira search for known disruption cards
- By default, the skill searches TRT and OCPBUGS for existing disruption cards after analysis

Implementation Steps

Step 1: Parse and Validate Input

Read the full file on GitHub · 777 lines

Files

What ships with it

6 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.

8d ago First seen · 777 lines · 32 tokens per session scan A 7761936efbb0

Subscribe to this mod's changes

analyze-disruption is a skill published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 4d ago), licensed Apache-2.0. It adds 32 tokens to every session and 9,536 once invoked, about $0.0002 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-30.

CI and CD Debugging DevOps and cloud

smoke-test

Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…

garrytan/gbrain · 79 tokens

mcore-create-issue

Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.

NVIDIA/skills · 26 tokens

debug-task

Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…

moonrepo/moon · 231 tokens

analyze-disruption