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.
npx agentmods add commands/wangke19/gemini-ai-helpers/statusgit 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/status)<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>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.00009 | $0.03071 |
| Opus 5 | $0.00005 | $0.01536 |
| Sonnet 5 | $0.00002 | $0.00614 |
| Haiku 4.5 | $0.00001 | $0.00307 |
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.
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:
-
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
-
Prerequisites Check:
- Verify
ocCLI is installed:which oc - Verify cluster access:
oc whoami - If not installed or not authenticated, provide clear instructions
- Verify
-
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
- If namespace provided, verify operator exists in that namespace:
-
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[]
- Channel:
- Get Subscription details:
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.
- 2d ago First seen · 352 lines · 9 tokens per session scan A b1e80e62abc8
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.
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'.
bmad-review-adversarial-general
Deprecated — forwards to bmad-review.
bmad-review-edge-case-hunter
Deprecated — forwards to bmad-review.