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 commands/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/commands/wangke19/gemini-ai-helpers/fetch-test-report)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/fetch-test-report"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/fetch-test-report.svg" alt="Measured on agentmods" 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.00017 | $0.00743 |
| Opus 5 | $0.00009 | $0.00371 |
| Sonnet 5 | $0.00003 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
fetch-test-report 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.
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.
This is a copy
94% identical to fetch-test-report — 8 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:fetch-test-report
Synopsis
/ci:fetch-test-report <test-name> [release]
Description
The ci:fetch-test-report command fetches a report for an OpenShift CI test by name from the Sippy API. It returns the test's BigQuery/Component Readiness test ID, Jira component, pass rates for the current and previous 7-day periods, and open bug counts. The open_bugs field counts Jira bugs that mention this test by name — this can help surface bugs that have been filed but not yet triaged in Component Readiness.
Implementation
-
Determine the release: If the user did not specify a release, use the
fetch-releasesskill to get the latest OCP release:release=$(python3 extensions/ci/skills/fetch-releases/fetch_releases.py --latest)If the user specified a release (e.g., "4.21"), use that value directly.
-
Fetch the test report: Use the
fetch-test-reportskill to query the Sippy tests API:python3 extensions/ci/skills/fetch-test-report/fetch_test_report.py "<test-name>" --release "$release" --format summaryTo see a per-variant breakdown (one row per variant combo), add
--no-collapse:python3 extensions/ci/skills/fetch-test-report/fetch_test_report.py "<test-name>" --release "$release" --no-collapse --format summary -
Present the results: Show the user the test report including test ID, pass rates, Jira component, open bugs, and trend. If
open_bugs > 0, note that existing Jira bugs mention this test — these may be relevant even if the regression hasn't been triaged in Component Readiness yet.
Return Value
- Format: Human-readable summary of the test report
- Key fields: test_id (BigQuery/Component Readiness ID), jira_component, current/previous pass rates, run counts, trend, open_bugs
- open_bugs: Count of Jira bugs mentioning this test by name — helps find bugs filed but not yet triaged in Component Readiness
- variants (with
--no-collapse): Per-variant breakdown showing which job types the test passes/fails in
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 · 68 lines · 17 tokens per session scan A a78bd5515712
fetch-test-report is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 743 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to fetch-test-report, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
red-team
description: "Red team AI system for vulnerabilities".
integration-test-cycle
Self-iterating integration test workflow with codebase exploration, test development, autonomous test-fix cycles, and reflection-driven strategy adjustment.
test
Write tests before implementation using Red-Green-Refactor.
bmad-review-verification-gap
Deprecated — forwards to bmad-review.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.