Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpersnpx agentmods add skills/wangke19/gemini-ai-helpers/fetch-test-reportWrote 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-test-report)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/fetch-test-report"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/fetch-test-report/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-test-report"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/fetch-test-report.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.00027 | $0.02540 |
| Opus 5 | $0.00014 | $0.01270 |
| Sonnet 5 | $0.00005 | $0.00508 |
| Haiku 4.5 | $0.00003 | $0.00254 |
Grade A, and why
Fetch Test Report 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 9d 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?release=4.22` This is a copy
100% identical to fetch-test-report — 14 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.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch Test Report
This skill fetches a report for an OpenShift CI test by its full name using the Sippy tests API. It returns test metadata including the BigQuery/Component Readiness test ID, Jira component, pass rates for the current and previous reporting periods, and open bug counts. The open_bugs field counts Jira bugs that mention this test by name, which can help surface bugs that have been filed but not yet triaged in Component Readiness.
When to Use This Skill
Use this skill when you need to:
- Look up a test's Component Readiness / BigQuery test ID (
test_id) - Check current and previous pass rates for a test
- Find the Jira component associated with a test
- Determine if a test is flaking, failing, or stable
- Get run counts and failure/flake breakdowns for a test
- Check if there are open Jira bugs mentioning this test (may not yet be triaged in Component Readiness)
- See a per-variant breakdown of pass rates to identify if the test fails only in certain job types
Prerequisites
-
Network Access: The Sippy API must be accessible at
https://sippy.dptools.openshift.org- No authentication required
- Check:
curl -s https://sippy.dptools.openshift.org/api/health?release=4.22
-
Python 3: Python 3.6 or later
- Check:
python3 --version - Uses only standard library (no external dependencies)
- Check:
Implementation Steps
Step 1: Determine the Release
If the user did not specify a release, use the fetch-releases skill to determine the latest OCP release:
release=$(python3 extensions/ci/skills/fetch-releases/fetch_releases.py --latest)
If the user specified a release, use that directly.
Step 2: Run the Python Script
The skill uses a Python script to query the Sippy tests API:
# Path to the Python script
script_path="extensions/ci/skills/fetch-test-report/fetch_test_report.py"
# Fetch test report in JSON format (collapsed — one row for the test across all variants)
python3 "$script_path" "<test_name>" --release "$release" --format json
# Or fetch as human-readable summary
python3 "$script_path" "<test_name>" --release "$release" --format summary
# Fetch per-variant breakdown (one row per variant combo — useful for identifying
# if the test is failing only in certain job types, e.g., aws vs metal, upgrade vs new-install)
python3 "$script_path" "<test_name>" --release "$release" --no-collapse --format json
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.
- 9d ago First seen · 260 lines · 27 tokens per session scan A f7f928af2ddf
Fetch Test Report is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 2,540 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to fetch-test-report, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
skillgrade-setup
Sets up and runs skillgrade evaluation pipelines for Agent Skills. Use when initializing eval configurations, running trials, reviewing results, or integrating with CI. Don't use for writing grader scripts, general test authoring, or non-agentic documentation.
onboard-repo
Index an unfamiliar codebase into the knowledge graph, then produce a first orientation map -- entry points, most-depended-upon modules, hotspots, test topology.
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
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.
exploit-xss
Cross-site scripting (XSS) vulnerability detection and exploitation. Supports reflected XSS, stored XSS, DOM-based XSS, and blind XSS testing. Use this skill when user mentions XSS, cross-site scripting, script injection, or needs to test JavaScript injection in parameters, forms, headers, or DOM sources.
platform-pre-review
Platform Developer: Stage 4a pre-review task. Run lint, type-check, SCA, license check, security trigger, and hygiene checks. Produce pipeline/gates/stage-04a.json.