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 fetch-job-run-summarygit 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/fetch-job-run-summary)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/fetch-job-run-summary"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/fetch-job-run-summary/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/fetch-job-run-summary"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/fetch-job-run-summary.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.00025 | $0.01324 |
| Opus 5 | $0.00013 | $0.00662 |
| Sonnet 5 | $0.00005 | $0.00265 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
fetch-job-run-summary 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 11d 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Fetch Job Run Summary — 97% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch Job Run Summary
This skill fetches a summary of a Prow job run from the Sippy API, listing all tests that failed (excluding flakes) along with their error messages.
When to Use This Skill
Use this skill when you need to:
- List all tests that failed in a specific Prow job run
- Understand which components are affected by failures in a job
- Identify dominant error patterns across multiple test failures
- Investigate mass test failure regressions by examining the underlying test failures
- Get a quick overview of a job run's health (pass rate, infrastructure failure, etc.)
Prerequisites
- Python 3: Version 3.6 or later
- Network Access: Must be able to reach
https://sippy.dptools.openshift.org
Implementation
script_path="plugins/ci/skills/fetch-job-run-summary/fetch_job_run_summary.py"
# Text output (AI-readable)
python3 "$script_path" <prow_job_run_id>
# JSON output (structured)
python3 "$script_path" <prow_job_run_id> --format json
Parameters
| Parameter | Required | Description |
|---|---|---|
prow_job_run_id |
Yes | The Prow job run ID (numeric, e.g., 2030845545290928128) |
--format |
No | Output format: text (default) or json |
Extracting a Job Run ID
The job run ID can be extracted from a Prow job URL:
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/<job-name>/<job_run_id>
The last path segment is the job run ID.
API Details
Endpoint: https://sippy.dptools.openshift.org/api/job/run/summary
Query Parameter: prow_job_run_id (required)
Response Fields:
| Field | Type | Description |
|---|---|---|
id |
int | Prow job run ID |
name |
string | Full job name |
release |
string | OpenShift release (e.g., 4.22) |
cluster |
string | Build cluster (e.g., build01) |
url |
string | Prow job URL |
startTime |
string | ISO 8601 start time |
durationSeconds |
int | Job duration in seconds |
overallResult |
string | S (success) or F (failure) |
reason |
string | Human-readable result reason |
infrastructureFailure |
bool | Whether this was an infrastructure failure |
testCount |
int | Total number of tests run |
testFailureCount |
int | Number of failed tests |
testFailures |
dict | Map of test name to error message (excludes flakes) |
variants |
list | Job variant tags |
What ships with it
1 file 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.
- 11d ago First seen · 146 lines · 25 tokens per session scan A fcdee424688f
fetch-job-run-summary is a skill published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 1,324 once invoked, about $0.0001 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.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.