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/checkgit 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/check)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/check"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/check.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 | $0.00008 | $0.01266 |
| Opus 5 | $0.00004 | $0.00633 |
| Sonnet 5 | $0.00002 | $0.00253 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade A, and why
check scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Suggest testing connectivity: `curl -v http://<gateway-address>` How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
gwapi:check
Synopsis
/gwapi:check [namespace]
Description
The gwapi:check command verifies the status of Gateway API resources in a Kubernetes or OpenShift cluster. It checks:
- Presence and status of GatewayClass resources
- Presence and status of Gateway resources
- Gateway listener configuration and readiness
- Gateway addresses and connectivity
This command helps troubleshoot Gateway API deployments and verify successful installation.
Arguments
$1(optional): Target namespace to check for Gateway resources. If not specified, checks all namespaces for GatewayClass (cluster-scoped) and Gateway resources.
Implementation
-
Tool Detection
- Check if
ocis available:which oc - If not available, check for
kubectl:which kubectl - If neither is available, inform the user to install one of these tools:
- Check if
-
Cluster Connection Verification
- Verify cluster connectivity:
oc whoamiorkubectl cluster-info - If connection fails, inform the user to authenticate to their cluster:
- For OpenShift:
oc login <cluster-url> - For Kubernetes: Configure kubeconfig properly
- For OpenShift:
- Verify cluster connectivity:
-
Check GatewayClass Resources
- List all GatewayClass resources:
oc get gatewayclassorkubectl get gatewayclass - For each GatewayClass found:
- Display name, controller, and ACCEPTED status
- Get detailed status:
oc get gatewayclass <name> -o yaml - Check the
status.conditionsfor any errors or warnings
- If no GatewayClass found:
- Display: "No GatewayClass resources found. You may need to install Gateway API CRDs or run /gwapi:install"
- List all GatewayClass resources:
-
Check Gateway Resources
- If namespace argument provided:
- Check Gateway resources in specified namespace:
oc get gateway -n <namespace>
- Check Gateway resources in specified namespace:
- If no namespace argument:
- Check all namespaces:
oc get gateway --all-namespaces
- Check all namespaces:
- For each Gateway found:
- Display name, namespace, class, and PROGRAMMED status
- Get detailed information:
oc get gateway <name> -n <namespace> -o yaml - Extract and display:
- Gateway addresses (LoadBalancer IPs/hostnames)
- Listener configurations (hostnames, ports, protocols)
- Listener status and attached routes count
- Check the
status.conditionsfor any errors or warnings
- If no Gateway found:
- Display: "No Gateway resources found in [namespace/cluster]"
- If namespace argument provided:
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.
- yesterday First seen · 148 lines · 8 tokens per session scan A e537ea0705c3
check is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,266 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
secrets
Provides tools for managing environment variables and secrets for your Supabase project.
test-ephemeral
Deploy and test a merge request in ephemeral environment.
vpn
Connect to Red Hat VPN for internal resources.
10_gofer_cloud
Deploy and configure the Gofer cloud integration for remote pipeline execution.
deploy-ai
description: "Deploy AI system to production".
checklist
Generate a custom checklist for the current feature based on user requirements.