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/listgit 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/list)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/list"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/list.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.00006 | $0.01523 |
| Opus 5 | $0.00003 | $0.00762 |
| Sonnet 5 | $0.00001 | $0.00305 |
| Haiku 4.5 | $0.00001 | $0.00152 |
Grade A, and why
list 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
olm:list
Synopsis
/olm:list [namespace] [--all-namespaces]
Description
The olm:list command lists all installed operators in an OpenShift cluster, showing their status, version, and namespace. This command provides a quick overview of the operator landscape in your cluster.
This command helps you:
- Discover what operators are currently installed
- Check operator versions and status at a glance
- Identify operators that may need attention (failed, upgrading, etc.)
- Get a comprehensive view across namespaces
The command presents information in an easy-to-read table format with key details about each operator's ClusterServiceVersion (CSV) and Subscription.
Implementation
The command performs the following steps:
-
Parse Arguments:
$1: Namespace (optional) - Target namespace to list operators from$2: Flag (optional):--all-namespacesor-A: List operators across all namespaces (default behavior if no namespace specified)
-
Prerequisites Check:
- Verify
ocCLI is installed:which oc - Verify cluster access:
oc whoami - If not installed or not authenticated, provide clear instructions
- Verify
-
Determine Scope:
- If namespace is specified: List operators only in that namespace
- If
--all-namespacesflag or no arguments: List operators cluster-wide - Default behavior: Show all operators across all namespaces
-
Fetch Operator Data:
- Get all ClusterServiceVersions (CSVs):
# For specific namespace oc get csv -n {namespace} -o json # For all namespaces oc get csv --all-namespaces -o json - Get all Subscriptions:
# For specific namespace oc get subscription -n {namespace} -o json # For all namespaces oc get subscription --all-namespaces -o json
- Get all ClusterServiceVersions (CSVs):
-
Parse and Correlate Data:
- For each CSV, extract:
- Name:
.metadata.name - Namespace:
.metadata.namespace - Display Name:
.spec.displayName - Version:
.spec.version - Phase/Status:
.status.phase(e.g., "Succeeded", "Installing", "Failed") - Install Time:
.metadata.creationTimestamp
- Name:
- For each Subscription, extract:
- Operator Name:
.spec.name - Channel:
.spec.channel - Source:
.spec.source - Installed CSV:
.status.installedCSV - Current CSV:
.status.currentCSV
- Operator Name:
- Correlate Subscriptions with CSVs to show complete operator information
- For each CSV, extract:
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 · 175 lines · 6 tokens per session scan A d8542619a9c5
list is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 1,523 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
spec-design
Create comprehensive technical design for a specification.
spec-kitty.implement
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
release-prod
Guide you through promoting stage → production.
claude-request
Send a prompt to Claude Code via the LLM gateway with session tracking.
modernize-extract-rules
Mine business logic from legacy code into testable, human-readable rule specifications.
mem-search
Full-text search in the memory vault (archives, contexts, histories, index).