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/wangke19/gemini-ai-helpersnpx agentmods add commands/wangke19/gemini-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/wangke19/gemini-ai-helpers/analyze)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/analyze"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-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.00027 | $0.06218 |
| Opus 5 | $0.00014 | $0.03109 |
| Sonnet 5 | $0.00005 | $0.01244 |
| Haiku 4.5 | $0.00003 | $0.00622 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 756 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
lvms:analyze
Synopsis
/lvms:analyze [must-gather-path] [--live] [--component <component>]
Description
The lvms:analyze command provides comprehensive troubleshooting for OpenShift LVMS (Logical Volume Manager Storage). It analyzes the health and configuration of LVMCluster, volume groups, PVCs, TopoLVM CSI driver, and node-level storage to identify and diagnose common LVMS issues.
The command can operate in two modes:
- Must-gather analysis: Analyzes LVMS must-gather data offline
- Live cluster analysis: Connects to a running cluster and performs real-time diagnostics
Common issues detected:
- PVCs stuck in Pending state
- LVMCluster not reaching Ready state
- Volume group creation failures
- Missing or unhealthy physical volumes
- TopoLVM CSI driver issues
- Node-level disk availability problems
- Thin pool configuration issues
- Device class misconfigurations
- Operator and vg-manager pod errors (from log analysis)
Prerequisites
For Live Cluster Analysis:
ocCLI installed and configured- Active cluster connection:
oc whoami - Read access to LVMS namespace (
openshift-lvm-storageor olderopenshift-storage) - Ability to read cluster-scoped resources (CRDs, Nodes, PVs)
For Must-Gather Analysis:
- LVMS must-gather data extracted to a directory
- Must-gather structure:
must-gather/ └── registry-ci-openshift-org.../ ├── cluster-scoped-resources/ ├── namespaces/ │ └── openshift-lvm-storage/ (or openshift-storage for older versions) └── ...
Namespace Compatibility:
- LVMS namespace changed from
openshift-storagetoopenshift-lvm-storagein recent versions - The command automatically detects which namespace is used in the must-gather
- Both namespaces are supported for backward compatibility
Analysis Script:
- Python 3 script at:
extensions/lvms/skills/lvms-analyzer/scripts/analyze_lvms.py - If script is missing, command will use built-in analysis logic
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 · 756 lines · 27 tokens per session scan A 9bd53968051e
analyze is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 6,218 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-03.
Other commands, from other repositories
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.
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.
create-docker-mcp-tunnel
Stand up an Google MCP tunnel locally with Docker Compose so Gemini can call a private MCP server (manual-credentials quickstart).
k8s-diag
Diagnoses failing Kubernetes pods, deployments, and cluster configurations.