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/analyze-prow-job-install-failure)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/analyze-prow-job-install-failure"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/analyze-prow-job-install-failure/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/commands/wangke19/gemini-ai-helpers/analyze-prow-job-install-failure"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/analyze-prow-job-install-failure.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.00010 | $0.01788 |
| Opus 5 | $0.00005 | $0.00894 |
| Sonnet 5 | $0.00002 | $0.00358 |
| Haiku 4.5 | $0.00001 | $0.00179 |
Grade A, and why
analyze-prow-job-install-failure 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.
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.
Name
ci:analyze-prow-job-install-failure
Synopsis
/ci:analyze-prow-job-install-failure <prowjob-url>
Description
The ci:analyze-prow-job-install-failure command analyzes OpenShift installation failures in Prow CI jobs by downloading and examining installer logs, log bundles, and sosreports (for metal jobs). This command is specifically designed to debug failures in the "install should succeed: overall" test, which indicates that the installation process failed at some stage.
Important: All "install should succeed" tests have a specific suffix indicating the failure stage (configuration, infrastructure, cluster bootstrap, cluster creation, cluster operator stability, or other). The JUnit XML contains both the specific failure reason test (which fails) and the overall test (which also fails when any stage fails). This command analyzes the specific failure stage to provide targeted diagnostics.
The command accepts:
- Prow job URL (required): URL to the failed CI job from prow.ci.openshift.org
It downloads relevant artifacts from Google Cloud Storage, analyzes them, and generates a comprehensive report with findings and recommended next steps.
Recognized Failure Modes
The command identifies the failure mode from junit_install.xml and tailors its analysis:
- "install should succeed: configuration" - Extremely rare failure where install-config.yaml validation failed. Focus on installer log only.
- "install should succeed: infrastructure" - Failed to create cloud resources. Usually due to cloud quota, rate limiting, or outages. Log bundle may not exist.
- "install should succeed: cluster bootstrap" - Bootstrap node failed to start temporary control plane. Check bootkube logs in the bundle.
- "install should succeed: cluster creation" - One or more operators unable to deploy. Check operator logs in gather-must-gather.
- "install should succeed: cluster operator stability" - Operators never stabilized (stuck progressing/degraded). Check operator status and logs.
- "install should succeed: other" - Unknown failure requiring comprehensive analysis of all available logs.
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 · 10 tokens per session scan A 61519a50601b
analyze-prow-job-install-failure is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 1,788 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-31.
Other commands, from other repositories
audit
Run a structured codebase audit. Maps the architecture, assesses health (compliance, tests, docs), performs deep analysis (security, performance, code quality), and synthesizes a prioritized roadmap. Outputs land under docs/audit/ in this project. Phases 0-3 with human checkpoints between each phase. Use /audit-quick…
wtfp:report-bug
Collect a reproducible bug report and publish it only after explicit user approval.
fix
Diagnose and fix bugs, errors, and issues in code.
bug-report
Structured bug-fix protocol per docs/methodology/bug-protocol.md. Use when asked to '/bug-report', 'I found a bug', 'something is broken', 'fix this bug', 'report a bug', 'this is broken'.
issue:discover-by-prompt
Discover issues from user prompt with Gemini-planned iterative multi-agent exploration. Uses ACE semantic search for context gathering and supports cross-module comparison (e.g., frontend vs backend API contracts).
issue:discover
Discover potential issues from multiple perspectives (bug, UX, test, quality, security, performance, maintainability, best-practices) using CLI explore. Supports Exa external research for security and best-practices perspectives.