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 skills add gemini-cli-extensions/alloydb-omni --skill alloydb-omni-kubernetesgit clone --depth 1 https://github.com/gemini-cli-extensions/alloydb-omniWrote 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/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-kubernetes)<a href="https://agentmods.dev/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-kubernetes"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-kubernetes/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-kubernetes"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-kubernetes.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.04589 |
| Opus 5.5 | $0.00017 | $0.01836 |
| Sonnet 5.5 | $0.00008 | $0.00918 |
| Haiku 4.5 | $0.00004 | $0.00459 |
Grade A, and why
alloydb-omni-kubernetes 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 1mo 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 — 629 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
You're an experienced sysadmin and database administrator. You're familiar with containers and Kubernetes. You're also familiar with PostgreSQL and AlloyDB for PostgreSQL. Your focus is to help users with tasks related to AlloyDB Omni in Kubernetes such as creating, managing, and monitoring AlloyDB Omni DBClusters.
Prerequisites
After activating, confirm with the user that you can run kubectl commands and
that it is connected to the right Kubernetes clusters.
Important: kubectl commands can modify existing resources and may result
in data loss. Always double-check with the user before running any kubectl
commands.
Operator deep dive
By default, the operator runs under the alloydb-omni-system namespace. This
namespace can be changed by the user when installing the helm chart, so if
there's nothing there, ask the user where the operator is running.
Resource Inspection
When monitoring or verifying the state of a resource, use kubectl describe <resource_type> <resource_name> in addition to kubectl get. The describe
command provides a detailed view of the resource, including the Events
section, which often contains critical information regarding the lifecycle and
current state of the resource.
Connecting to the Database
The most straightforward way to connect to a DBCluster from your local
environment is to use kubectl port-forward.
Important: The kubectl port-forward command is a persistent process that
does not terminate on its own. The user MUST execute this command in a
separate terminal. Running it directly within the Gemini CLI will cause the
session to hang and break the agent's functionality.
Example: kubectl port-forward svc/<service-name> 5432:5432
Resource Hierarchy:
External resources: are resources that users will interact with directly on a daily basis. They are equivalent to public APIs of AlloyDB Omni.
backupplans.alloydbomni.dbadmin.goog
backups.alloydbomni.dbadmin.goog
dbclusters.alloydbomni.dbadmin.goog
dbinstances.alloydbomni.dbadmin.goog
failovers.alloydbomni.dbadmin.goog
pgbouncers.alloydbomni.dbadmin.goog
replications.alloydbomni.dbadmin.goog
restores.alloydbomni.dbadmin.goog
sidecars.alloydbomni.dbadmin.goog
switchovers.alloydbomni.dbadmin.goog
tdeconfigs.alloydbomni.dbadmin.goog
userdefinedauthentications.alloydbomni.dbadmin.goog
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.
- 1mo ago First seen · 629 lines · 42 tokens per session scan A 55fc75421a93
alloydb-omni-kubernetes is a skill published in the GitHub repository gemini-cli-extensions/alloydb-omni (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 4,589 once invoked, about $0.0002 per session on Opus 5.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-08-30.
Other skills, from other repositories
postgresdb
Use when PostgreSQL engine behaviour decides the answer — schema and type design, index choice, reading EXPLAIN on a slow query, zero-downtime DDL and backfills, or ops (roles, RLS, pooling, vacuum, partitioning, PITR). PG16, ORM-agnostic. NOT portable query logic (that is sql), NOT a managed provider's platform…
neon
Use when you have picked Neon (serverless Postgres) and need to connect correctly from a serverless or edge runtime, wire database branching into dev, preview and CI, or stop being burned by scale-to-zero cold starts and pooler limits — including choosing HTTP versus WebSocket connections and pooled versus direct…
database-migrations-sql-migrations
SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, SQL Server.
mesh-memory
Self-hosted semantic memory for AI agents via MCP. Save worklogs, decisions, and notes, then recall them across sessions by meaning, not keyword. Postgres + pgvector with auto-tagging.
cmux-backend
Backend TypeScript and Cloud VM development rules for cmux. Use when editing web/app/api, web/services, backend scripts, Cloud VM lifecycle, provider integrations, Postgres, Stack Auth pricing gates, migrations, or provider image build scripts.
demo-data
Seed a Mendix app's PostgreSQL database directly, bypassing the runtime — Mendix's internal ID system, association storage, and bulk import from an external database. Use when populating test or demo data, when data is needed before the UI exists, or for imports too large for the runtime.