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/upgrade)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/upgrade"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/upgrade.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.00010 | $0.02895 |
| Opus 5 | $0.00005 | $0.01448 |
| Sonnet 5 | $0.00002 | $0.00579 |
| Haiku 4.5 | $0.00001 | $0.00290 |
Grade A, and why
upgrade 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
olm:upgrade
Synopsis
/olm:upgrade <operator-name> [namespace] [--channel=<channel>] [--approve]
Description
The olm:upgrade command updates an installed operator to the latest version in its current channel or switches to a different channel. It can also approve pending InstallPlans for operators with manual approval mode.
This command helps you:
- Update operators to the latest version in their channel
- Switch operators to different channels (e.g., stable to tech-preview)
- Approve pending upgrade InstallPlans for manual approval mode
- Monitor upgrade progress
- Rollback on failure (if possible via OLM)
Implementation
The command performs the following steps:
-
Parse Arguments:
$1: Operator name (required) - Name of the operator to upgrade$2: Namespace (optional) - Namespace where operator is installed- If not provided, searches for the operator across all namespaces
$3+: Flags (optional):--channel=<channel-name>: Switch to a different channel--approve: Automatically approve pending InstallPlan (for manual approval mode)
-
Prerequisites Check:
- Verify
ocCLI is installed:which oc - Verify cluster access:
oc whoami - Check if user has sufficient privileges
- Verify
-
Locate Operator:
- If namespace provided, verify operator exists:
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, prompt user to specify namespace
- If namespace provided, verify operator exists:
-
Get Current State:
- Get current Subscription:
oc get subscription {operator-name} -n {namespace} -o json - Extract:
- Current channel:
.spec.channel - Install plan approval:
.spec.installPlanApproval - Installed CSV:
.status.installedCSV - Current CSV:
.status.currentCSV
- Current channel:
- Get current CSV version:
oc get csv {installed-csv} -n {namespace} -o jsonpath='{.spec.version}'
- Get current Subscription:
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 · 350 lines · 10 tokens per session scan A fa0c02a2ea76
upgrade is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 2,895 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
5_gofer_implement
Execute all tasks from tasks.md phase by phase with feedback loops and engineering review.
eai-update
Use this command to install or update EAI Gofer for the current AI coding app. This command works without an EAI project, a Gofer scaffold, or EAI sign-in.
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).
bmad-agent-pm
Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
help
Get help with the hookify plugin.