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/uninstall)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/uninstall"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/uninstall.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.00012 | $0.03575 |
| Opus 5 | $0.00006 | $0.01788 |
| Sonnet 5 | $0.00002 | $0.00715 |
| Haiku 4.5 | $0.00001 | $0.00358 |
Grade A, and why
uninstall 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
olm:uninstall
Synopsis
/olm:uninstall <operator-name> [namespace] [--remove-crds] [--remove-namespace]
Description
The olm:uninstall command uninstalls a day-2 operator from an OpenShift cluster by removing its Subscription, ClusterServiceVersion (CSV), and optionally its Custom Resource Definitions (CRDs) and namespace.
This command provides a comprehensive uninstallation workflow:
- Removes the operator's Subscription
- Deletes the ClusterServiceVersion (CSV)
- Optionally removes operator-managed deployments
- Optionally deletes Custom Resource Definitions (CRDs)
- Optionally removes the operator's namespace
- Provides detailed feedback on each step
The command is designed to safely clean up operators installed via OLM, with optional flags for thorough cleanup of all operator-related resources.
Implementation
The command performs the following steps:
-
Parse Arguments:
$1: Operator name (required) - The name of the operator to uninstall$2: Namespace (optional) - The namespace where operator is installed. If not provided, defaults to{operator-name}-operator$3+: Flags (optional):--remove-crds: Remove Custom Resource Definitions after uninstalling--remove-namespace: Remove the operator's namespace after cleanup--force: Skip confirmation prompts
-
Prerequisites Check:
- Verify
ocCLI is installed:which oc - Verify cluster access:
oc whoami - Check if user has cluster-admin or sufficient privileges
- Verify
-
Verify Operator Installation:
- Check if namespace exists:
oc get namespace {namespace} --ignore-not-found - Check if subscription exists:
oc get subscription {operator-name} -n {namespace} --ignore-not-found - If not found, display error: "Operator {operator-name} is not installed in namespace {namespace}"
- List what will be uninstalled
- Check if namespace exists:
-
Display Uninstallation Plan:
- Show operator details:
oc get subscription {operator-name} -n {namespace} -o yaml oc get csv -n {namespace} - Display what will be removed:
- Subscription name and namespace
- CSV name and version
- Deployments (if any)
- CRDs (if
--remove-crdsflag is set) - Namespace (if
--remove-namespaceflag is set)
- Show operator 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.
- 4d ago First seen · 393 lines · 12 tokens per session scan A 0659fc3bb23d
uninstall is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 3,575 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.