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.
git clone --depth 1 https://github.com/wangke19/gemini-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/wangke19/gemini-ai-helpers/query-test-result)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/query-test-result"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/query-test-result.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.00011 | $0.02493 |
| Opus 5 | $0.00005 | $0.01247 |
| Sonnet 5 | $0.00002 | $0.00499 |
| Haiku 4.5 | $0.00001 | $0.00249 |
Grade A, and why
query-test-result 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
100% identical to query-test-result — 0 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:query-test-result
Synopsis
/ci:query-test-result <version> <keywords> [sippy-url]
Description
The ci:query-test-result command queries OpenShift CI test results from Sippy based on the OpenShift version and test name keywords. It retrieves test statistics including pass rate, number of runs, failures, and links to failed job runs.
By default, it queries the production Sippy instance at sippy.dptools.openshift.org. You can optionally specify a different Sippy instance URL to query alternative environments (e.g., QE component readiness).
This command is useful for:
- Checking the health of specific test cases
- Finding test failure patterns
- Getting links to failed Prow job runs for debugging
- Monitoring test regression trends
- Querying different Sippy instances (production, QE, etc.)
Arguments
$1(version): OpenShift version to query (e.g., "4.21", "4.20", "4.19")$2(keywords): Keywords to search in test names (e.g., "PolarionID:81664", "olmv1", "sig-storage")$3(sippy-url) [optional]: Sippy instance base URL. Defaults to "sippy.dptools.openshift.org" if not provided. Examples: "qe-component-readiness.dptools.openshift.org"
Implementation
-
Parse Arguments
- Extract version from
$1(e.g., "4.21") - Extract keywords from
$2(e.g., "81664" or "olmv1") - Extract Sippy URL from
$3if provided, otherwise use default "sippy.dptools.openshift.org" - Normalize URL to extract base domain for API endpoint (strip "/sippy-ng/" suffix if present)
- Add "https://" prefix if not already present
- Extract version from
-
Build Sippy API Request
- Construct filter JSON for the
/api/testsendpoint:filters = { "items": [ { "columnField": "name", "not": False, "operatorValue": "contains", "value": keywords } ], "linkOperator": "and" } - Set query parameters:
release: The OpenShift versionfilter: JSON-encoded filter objectsort: "asc"sortField: "net_improvement"
- Construct filter JSON for the
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 · 248 lines · 11 tokens per session scan A 7729cbaa76b2
query-test-result is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 2,493 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to query-test-result, differing in 0 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.
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.
specify
Create or update the feature specification from a natural language feature description.