Must-Gather Analyzer

Must-Gather Analyzer is a skill for Claude Code, Codex from wangke19/gemini-ai-helpers. It costs 126 tokens per session (2,121 once invoked), scanned A, a copy of must-gather-analyzer, Apache-2.0.

A diagnostic tool for examining OpenShift cluster data saved by must-gather. OpenShift is a platform for running containers, and must-gather is a support bundle containing cluster information.

In plain words
What is it for?
It is used to investigate cluster health and troubleshoot failures from an offline must-gather directory.
Why use it?
It helps identify unhealthy operators, pods, nodes, networking, storage, events, and etcd problems from collected data.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is used to investigate cluster health and troubleshoot failures from an offline must-gather directory.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wangke19/gemini-ai-helpers/must-gather-analyzer
Install

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.

Any agent
npx skills add wangke19/gemini-ai-helpers --skill must-gather-analyzer
Clone the repo
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for Must-Gather Analyzer

README.md
[![agentmods](https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/must-gather-analyzer/github.svg)](https://agentmods.dev/skills/wangke19/gemini-ai-helpers/must-gather-analyzer)
Your own site
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/must-gather-analyzer"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/must-gather-analyzer/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.

agentmods 80×15 button for Must-Gather Analyzer

Your own site · 80×15
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/must-gather-analyzer"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/must-gather-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,121 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00126 $0.02121
Opus 5 $0.00063 $0.01060
Sonnet 5 $0.00025 $0.00424
Haiku 4.5 $0.00013 $0.00212

Measured 7d ago against content hash 7d269e9a90a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

Must-Gather Analyzer 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 7d ago.

The scan reads SKILL.md. This mod also ships 11 executable files (scripts/analyze_clusteroperators.py, scripts/analyze_clusterversion.py, scripts/analyze_etcd.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

97% identical to must-gather-analyzer — 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.

extensions/must-gather/skills/must-gather-analyzer/SKILL.md · 286 lines

How it starts

The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Must-Gather Analyzer Skill

Comprehensive analysis of OpenShift must-gather diagnostic data with helper scripts that parse YAML and display output in oc-like format.

Overview

This skill provides analysis for:

  • ClusterVersion: Current version, update status, and capabilities
  • Cluster Operators: Status, degradation, and availability
  • Pods: Health, restarts, crashes, and failures across namespaces
  • Nodes: Conditions, capacity, and readiness
  • Network: OVN/SDN diagnostics and connectivity
  • Events: Warning and error events across namespaces
  • etcd: Cluster health, member status, and quorum
  • Storage: PersistentVolumes and PersistentVolumeClaims status

Must-Gather Directory Structure

Important: Must-gather data is contained in a subdirectory with a long hash name:

must-gather/
└── registry-ci-openshift-org-origin-...-sha256-<hash>/
    ├── cluster-scoped-resources/
    │   ├── config.openshift.io/clusteroperators/
    │   └── core/nodes/
    ├── namespaces/
    │   └── <namespace>/
    │       └── pods/
    │           └── <pod-name>/
    │               └── <pod-name>.yaml
    └── network_logs/

The analysis scripts expect the path to the subdirectory (the one with the hash), not the root must-gather folder.

Instructions

1. Get Must-Gather Path

Ask the user for the must-gather directory path if not already provided.

  • If they provide the root directory, look for the subdirectory with the hash name
  • The correct path contains cluster-scoped-resources/ and namespaces/ directories

2. Choose Analysis Type

Based on user's request, run the appropriate helper script:

ClusterVersion Analysis
./scripts/analyze_clusterversion.py <must-gather-path>

Shows cluster version information similar to oc get clusterversion:

  • Current version and update status
  • Progressing state
  • Available updates
  • Version conditions
  • Enabled capabilities
  • Update history
Cluster Operators Analysis
./scripts/analyze_clusteroperators.py <must-gather-path>

Read the full file on GitHub · 286 lines

Changes

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.

  1. 7d ago First seen · 286 lines · 126 tokens per session scan A 7d269e9a90a4

Subscribe to this mod's changes

Must-Gather Analyzer is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 126 tokens to every session and 2,121 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to must-gather-analyzer, differing in 8 lines, and is treated as a copy.