status

status is a command for Claude Code from wangke19/gemini-ai-helpers. It costs 9 tokens per session (3,071 once invoked), scanned A, original, Apache-2.0.

A detailed status command for an operator installed in an OpenShift cluster. It examines the operator’s installation records, deployments, pods, events, and available updates.

In plain words
What is it for?
Use it to inspect a specific operator’s version, subscriptions, install plans, workloads, recent events, and configuration-related resource problems.
Why use it?
It collects the information needed to understand whether an operator is healthy and where an installation or upgrade is failing.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

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.

agentmods
npx agentmods add commands/wangke19/gemini-ai-helpers/status
Clone the repo
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers

Made for: Claude Code.

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 status

README.md
[![agentmods](https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/status.svg)](https://agentmods.dev/commands/wangke19/gemini-ai-helpers/status)
Your own site
<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/status"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/status.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,071 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00009 $0.03071
Opus 5 $0.00005 $0.01536
Sonnet 5 $0.00002 $0.00614
Haiku 4.5 $0.00001 $0.00307

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

Security

Grade A, and why

status 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 2d 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.

extensions/olm/commands/status.md · 352 lines

How it starts

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

Name

olm:status

Synopsis

/olm:status <operator-name> [namespace]

Description

The olm:status command provides comprehensive health and status information for a specific operator in an OpenShift cluster. It displays detailed information about the operator's CSV, Subscription, InstallPlan, deployments, and pods to help diagnose issues and verify proper operation.

This command helps you:

  • Check if an operator is running correctly
  • Diagnose installation or upgrade problems
  • View operator version and available updates
  • Inspect operator deployments and pods
  • Review recent events and conditions
  • Identify resource issues or configuration problems

Implementation

The command performs the following steps:

  1. Parse Arguments:

    • $1: Operator name (required) - Name of the operator to inspect
    • $2: Namespace (optional) - Namespace where operator is installed
      • If not provided, searches for the operator across all namespaces
      • If multiple instances found, prompts user to specify namespace
  2. Prerequisites Check:

    • Verify oc CLI is installed: which oc
    • Verify cluster access: oc whoami
    • If not installed or not authenticated, provide clear instructions
  3. Locate Operator:

    • If namespace provided, verify operator exists in that namespace:
      oc get subscription {operator-name} -n {namespace} --ignore-not-found
      
    • If no namespace provided, search across all namespaces:
      oc get subscription --all-namespaces -o json | jq -r '.items[] | select(.spec.name=="{operator-name}") | .metadata.namespace'
      
    • If not found, display error with suggestions
    • If multiple instances found, list them and ask user to specify namespace
  4. Gather Subscription Information:

    • Get Subscription details:
      oc get subscription {operator-name} -n {namespace} -o json
      
    • Extract:
      • Channel: .spec.channel
      • Install Plan Approval: .spec.installPlanApproval
      • Source: .spec.source
      • Source Namespace: .spec.sourceNamespace
      • Installed CSV: .status.installedCSV
      • Current CSV: .status.currentCSV
      • State: .status.state
      • Conditions: .status.conditions[]

Read the full file on GitHub · 352 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. 2d ago First seen · 352 lines · 9 tokens per session scan A b1e80e62abc8

Subscribe to this mod's changes

status is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 3,071 once invoked, about $0.0000 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.