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/openshift-eng/ai-helpersnpx agentmods add commands/openshift-eng/ai-helpers/analyzeWrote 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/analyze)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/analyze"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/analyze.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.02313 |
| Opus 5 | $0.00009 | $0.01156 |
| Sonnet 5 | $0.00003 | $0.00463 |
| Haiku 4.5 | $0.00002 | $0.00231 |
Grade A, and why
analyze 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 3d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
must-gather:analyze
Synopsis
/must-gather:analyze [must-gather-path] [component]
Description
The analyze command performs comprehensive analysis of OpenShift must-gather diagnostic data. It runs specialized Python analysis scripts to extract and summarize cluster health information across multiple components.
The command can analyze:
- Cluster version and update status
- Cluster operator health (degraded, progressing, unavailable)
- Node conditions and resource status
- Pod failures, restarts, and crash loops
- Network configuration and OVN health
- OVN databases - logical topology, ACLs, pods
- Kubernetes events (warnings and errors)
- etcd cluster health and quorum status
- Persistent volume and claim status
- Prometheus alerts
You can request analysis of the entire cluster or focus on a specific component.
Prerequisites
Required Directory Structure:
Must-gather data typically has this structure:
must-gather/
└── registry-ci-openshift-org-origin-...-sha256-<hash>/
├── cluster-scoped-resources/
├── namespaces/
└── ...
The actual must-gather directory is the subdirectory with the hash name, not the parent directory.
Required Scripts:
Analysis scripts are bundled with this plugin at:
<plugin-root>/skills/must-gather-analyzer/scripts/
├── analyze_clusterversion.py
├── analyze_clusteroperators.py
├── analyze_nodes.py
├── analyze_pods.py
├── analyze_network.py
├── analyze_ovn_dbs.py
├── analyze_events.py
├── analyze_etcd.py
└── analyze_pvs.py
Where <plugin-root> is the directory where this plugin is installed (typically ~/.cursor/commands/ai-helpers/plugins/must-gather/ or similar).
Error Handling
CRITICAL: Script-Only Analysis
- NEVER attempt to analyze must-gather data directly using bash commands, grep, or manual file reading
- ONLY use the provided Python scripts in
plugins/must-gather/skills/must-gather-analyzer/scripts/ - If scripts are missing or not found:
- Stop immediately
- Inform the user that the analysis scripts are not available
- Ask the user to ensure the scripts are installed at the correct path
- Do NOT attempt alternative approaches
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.
- 3d ago First seen · 268 lines · 17 tokens per session scan A bc11bf630e42
analyze is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,313 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-09-05.
Other commands, from other repositories
System Status
Check overall system health and status.
investigate
Start a deep root-cause investigation on the AWS DevOps Agent and stream progress.
cloudflare-queues:troubleshoot
Quick troubleshooting for common Cloudflare Queues issues.
cloudflare-workers:debug
Interactive debugging workflow for Cloudflare Workers. Diagnoses deployment errors, runtime issues, and performance problems with step-by-step fixes.
cloudflare-workflows:debug
Interactive debugging for failing workflow instances. Use when user reports workflow errors, instances stuck, or deployment failures.
cloud-run-debug
Diagnose a failing Cloud Run service — Antigravity (agy/Gemini) digests the error logs cheaply, Claude infers the root cause and proposes a fix. Read-only by default; --apply writes the fix to a branch.