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.
git 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/catalog)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/catalog"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/catalog.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.00008 | $0.03065 |
| Opus 5 | $0.00004 | $0.01533 |
| Sonnet 5 | $0.00002 | $0.00613 |
| Haiku 4.5 | $0.00001 | $0.00307 |
Grade A, and why
catalog 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 — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
olm:catalog
Synopsis
/olm:catalog list
/olm:catalog add <name> <image> [--namespace=openshift-marketplace]
/olm:catalog remove <name> [--namespace=openshift-marketplace]
/olm:catalog refresh <name> [--namespace=openshift-marketplace]
/olm:catalog status <name> [--namespace=openshift-marketplace]
Description
The olm:catalog command manages catalog sources for operator discovery and installation. Catalog sources provide the list of operators available for installation in the cluster.
This command helps you:
- List all available catalog sources and their health status
- Add custom or private catalog sources
- Remove catalog sources
- Refresh catalog sources to get latest operator updates
Implementation
Subcommand: list
-
Get All CatalogSources:
oc get catalogsource -n openshift-marketplace -o json -
Parse CatalogSource Data: For each catalog, extract:
- Name:
.metadata.name - Display Name:
.spec.displayName - Publisher:
.spec.publisher - Source Type:
.spec.sourceType(grpc, configmap, etc.) - Image:
.spec.image(for grpc type) - Connection State:
.status.connectionState.lastObservedState - Last Updated:
.status.connectionState.lastUpdatedTime - Number of Operators: Count from PackageManifests with this catalog
- Name:
-
Get Catalog Pod Status:
oc get pods -n openshift-marketplace -l olm.catalogSource={catalog-name} -
Format Output:
═══════════════════════════════════════════════════════════ CATALOG SOURCES ═══════════════════════════════════════════════════════════ NAME STATUS OPERATORS LAST UPDATED SOURCE TYPE redhat-operators READY 150 2h ago grpc certified-operators READY 45 3h ago grpc community-operators READY 200 1h ago grpc redhat-marketplace READY 30 4h ago grpc custom-catalog FAILED 0 - grpc ═══════════════════════════════════════════════════════════ DETAILS ═══════════════════════════════════════════════════════════ redhat-operators: Display Name: Red Hat Operators Publisher: Red Hat Image: registry.redhat.io/redhat/redhat-operator-index:v4.20 Pod: redhat-operators-abc123 (Running) custom-catalog (FAILED): Display Name: Custom Catalog Publisher: My Company Image: registry.example.com/custom-catalog:latest Pod: custom-catalog-xyz789 (CrashLoopBackOff) Error: ImagePullBackOff To troubleshoot: /olm:catalog status custom-catalog
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 · 434 lines · 8 tokens per session scan A 7cf44fd3fdb1
catalog is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 3,065 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
projects
Provides tools for creating and managing your Supabase projects.
session-list
List recent sessions from the project ledger and offer to view one.
7a_stakeholder_comms
Generate stakeholder-facing communications: release notes, demo scripts, and change briefs.
convert-to-plan
Convert planning artifacts (lite-plan, workflow session, markdown) to issue solutions.
execute
Execute queue with DAG-based parallel orchestration (one commit per solution).
queue
Form execution queue from bound solutions using issue-queue-agent (solution-level).