What is alloydb-omni-container?

A guide for running AlloyDB Omni, a downloadable version of Google's AlloyDB database based on PostgreSQL, inside a container such as Docker or Podman. It covers local or offline database use.

Use it to start, stop, list, connect to, and inspect logs from AlloyDB Omni containers.

It provides the commands and guidance needed to manage a database container without manually working out each operation. The container setup is intended for development, not production workloads.

alloydb-omni-container — Skill for Claude Code by gemini-cli-extension

Install

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.

Any agent

npx skills add gemini-cli-extensions/alloydb-omni --skill alloydb-omni-container

Clone the repo

git clone --depth 1 https://github.com/gemini-cli-extensions/alloydb-omni

Made for: Claude Code.

Or install alloydb-omni, the plugin that ships this one along with the rest of its 2 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-container/github.svg)](https://agentmods.dev/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-container)

Your own site

<a href="https://agentmods.dev/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-container"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-container/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-container"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/alloydb-omni/alloydb-omni-container.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,264 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00051	$0.01264
Opus 5	$0.00026	$0.00632
Sonnet 5	$0.00010	$0.00253
Haiku 4.5	$0.00005	$0.00126

Measured 11d ago against content hash 97a4576f85b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

alloydb-omni-container 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 11d 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.

skills/alloydb-omni-container/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 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 container and container runtime technologies such as Docker, Podman, containerd, etc. You're also familiar with PostgreSQL and AlloyDB for PostgreSQL. Your focus is to help users with tasks related to AlloyDB Omni running in a container such as starting, stopping, listing, connecting to AlloyDB Omni instance running in a container, and querying for logs.

AlloyDB Omni is a downloadable database software package that offers a streamlined version of AlloyDB for PostgreSQL for deployment in a standalone instance in your environment. The container deployment model is the most lightweight and easiest way to get started with AlloyDB Omni, especially for offline / local development uses. However, this model lacks many high-end features such as high availability, automated backups, etc. and therefore it's not appropriate for production workloads.

Workflows

You have the following workflows:

Running a new AlloyDB Omni container.
Checking the status of an existing AlloyDB Omni container.
Stopping and removing an existing AlloyDB Omni container.
Connecting to an existing AlloyDB Omni container.

Running a new AlloyDB Omni container

Ask the user what version of AlloyDB Omni they want to run. If the user doesn't have a preference, suggest to use the latest version, or to refer to the documentation page for a list of supported versions: https://docs.cloud.google.com/alloydb/omni/containers/current/docs/overview. Use this as the IMAGE_TAG placeholder.
Ask the user for a name for the container. Suggest alloydb-omni as a default. Use this as the CONTAINER_NAME placeholder.
Ask the user where to store the database's data directory. If the user doesn't have a preference, suggest to create one for them under ~/alloydb-omni/data/<version>/. Use this as the DATA_DIR placeholder. Note: Before running the container, check if the <DATA_DIR> exists. If it doesn't, create it using mkdir -p <DATA_DIR>.
Ask the user what the password to set for the default postgres user. Use this as the DATABASE_PASSWORD placeholder.
Ask the user do they prefer to use docker or podman to run the container.

Read the full file on GitHub · 124 lines

Changes

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.

11d ago First seen · 124 lines · 51 tokens per session scan A 97a4576f85b1

Subscribe to this mod's changes

alloydb-omni-container is a skill published in the GitHub repository gemini-cli-extensions/alloydb-omni (4 stars, last pushed 6d ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,264 once invoked, about $0.0003 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-08-30.

Claude Code Containers Databases DevOps and cloud PostgreSQL alloydb antigravity cli codex gemini

alloydb-omni-container

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Context

Workflows

Running a new AlloyDB Omni container

What this file has done since we first saw it

Other skills, from other repositories

postgresql

cockroachdb

cosmosdb

supabase

timescaledb

neon