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 openshift-eng/ai-helpers --skill prow-job-analysisgit clone --depth 1 https://github.com/openshift-eng/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/openshift-eng/ai-helpers/prow-job-analysis)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/prow-job-analysis"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/prow-job-analysis/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/openshift-eng/ai-helpers/prow-job-analysis"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/prow-job-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.04593 |
| Opus 5.5 | $0.00006 | $0.01837 |
| Sonnet 5.5 | $0.00003 | $0.00919 |
| Haiku 4.5 | $0.00002 | $0.00459 |
Grade A, and why
prow-job-analysis 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 4d 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.
(stdlib-only `list`/`search`/`fetch`; `fetch --tail` reads a log's end) or `curl` against How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prow Job Analysis
Analyze failures in OpenShift Prow CI jobs. Identify the job type, inspect artifacts, classify the failure, and route to the specialized reference for deep analysis.
Input Format
The user will provide:
-
Prow job URL (required) — Prow UI or gcsweb URL
https://prow.ci.openshift.org/view/gs/test-platform-results-public/logs/<job>/<build_id>https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results-public/...
-
Test name (optional) — specific failed test to focus on
-
Flags (optional):
--backends <list>— focus disruption analysis on specific backends
Prerequisites
- Python 3.7+:
which python3 - jq:
which jq - gcloud CLI (recommended, not required):
which gcloud— fastest access to the public bucket (no auth required). Without it, every artifact operation works over plain HTTPS: prow_job_artifact_search.py (stdlib-onlylist/search/fetch;fetch --tailreads a log's end) orcurlagainsthttps://storage.googleapis.com/test-platform-results-public/....
Investigation Workflow
Step 1: Parse URL and Extract Metadata
- Find
/view/gs/<bucket>/(Prow UI) or/gcs/<bucket>/(gcsweb) in the URL. Any non-empty bucket segment is accepted. - Extract the object path after the bucket name, then
build_id— pattern(\d{10,})in the path. - Construct GCS base:
gs://{bucket}/{bucket-path}/using the URL bucket as-is, includingprow-artifact-archive. A private bucket will 403.
Step 2: Fetch prowjob.json
Use the fetch-prowjob-json skill to get job metadata. Extract:
- Job name from
.spec.job - Target from
--target=in ci-operator args - Job state from
.status.state - Refs (org, repo, PR number) from
.spec.refs
Step 3: Read the Pre-Digested Failure Summaries
openshift-tests and the gather steps already summarize most of what you need. Read these small (KB-sized) files before downloading logs, journals, or must-gather — they usually name the failed step, the failed tests, the cluster shape, and known failure signatures. Each may be absent; absence is itself a signal (noted below).
What ships with it
18 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.
- prow_job_artifact_search.py 23 KB runs code
- references/aggregated.md 26 KB
- references/alerts.md 8.5 KB
- references/artifacts.md 40 KB
- references/ci-infrastructure-changes.md 44 KB
- references/cloud-provider-errors.md 17 KB
- references/disruption.md 52 KB
- references/flaky-test-identification.md 17 KB
- references/hypershift.md 13 KB
- references/install/general.md 40 KB
- references/install/metal.md 40 KB
- references/networking.md 20 KB
- references/operating-system-changes.md 12 KB
- references/resource-exhaustion.md 22 KB
- references/test-extension-binaries.md 30 KB
- references/test-failure.md 14 KB
- references/upgrade.md 48 KB
- test_prow_job_artifact_search.py 4.4 KB runs code
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.
- 4d ago Changed · +85 lines b44baed0ece0
- 1mo ago Changed · +4 lines dda7ed4004b6
- 1mo ago First seen · 188 lines · 16 tokens per session scan A ca679a9dc56d
prow-job-analysis is a skill published in the GitHub repository openshift-eng/ai-helpers (119 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 4,593 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.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.