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 agentmods add commands/openshift-eng/ai-helpers/fetch-test-reportgit 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/commands/openshift-eng/ai-helpers/fetch-test-report)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/fetch-test-report"><img src="https://agentmods.dev/badge/commands/openshift-eng/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 | $0.00017 | $0.00741 |
| Opus 5 | $0.00009 | $0.00370 |
| Sonnet 5 | $0.00003 | $0.00148 |
| 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 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.
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-test-report — 94% identical, 8 lines differ
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 plugins/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 plugins/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 plugins/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, 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.
- 4d ago First seen · 68 lines · 17 tokens per session scan A 3488be0843fb
fetch-test-report is a command published in the GitHub repository openshift-eng/ai-helpers (114 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 741 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.