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 tmolavi/mcp-agent-skills-hub --skill alloydb-omni-optimizegit clone --depth 1 https://github.com/tmolavi/mcp-agent-skills-hubWrote 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/tmolavi/mcp-agent-skills-hub/alloydb-omni-optimize)<a href="https://agentmods.dev/skills/tmolavi/mcp-agent-skills-hub/alloydb-omni-optimize"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/alloydb-omni-optimize/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/tmolavi/mcp-agent-skills-hub/alloydb-omni-optimize"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/alloydb-omni-optimize.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.00038 | $0.00558 |
| Opus 5 | $0.00019 | $0.00279 |
| Sonnet 5 | $0.00008 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
alloydb-omni-optimize 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 12d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage
All scripts can be executed using Node.js. Replace <param_name> and
<param_value> with actual values.
Bash: node <skill_dir>/scripts/<script_name>.js '{"<param_name>": "<param_value>"}'
PowerShell: node <skill_dir>/scripts/<script_name>.js '{\"<param_name>\": \"<param_value>\"}'
Note: The scripts automatically load the environment variables from various .env files. Do not ask the user to set vars unless skill executions fails due to env var absence.
Scripts
list_autovacuum_configurations
List PostgreSQL autovacuum-related configurations (name and current setting) from pg_settings.
list_available_extensions
Discover all PostgreSQL extensions available for installation on this server, returning name, default_version, and description.
list_columnar_configurations
List AlloyDB Omni columnar-related configurations (name and current setting) from pg_settings.
list_columnar_recommended_columns
Lists columns that AlloyDB Omni recommends adding to the columnar engine to improve query performance.
list_installed_extensions
List all installed PostgreSQL extensions with their name, version, schema, owner, and description.
list_memory_configurations
List PostgreSQL memory-related configurations (name and current setting) from pg_settings.
list_pg_settings
Parameters
| Name | Type | Description | Required | Default |
|---|---|---|---|---|
| setting_name | string | Optional: A | No | |
| : : : specific : : : | ||||
| : : : configuration : : : | ||||
| : : : parameter : : : | ||||
| : : : name pattern : : : | ||||
| : : : to search : : : | ||||
| : : : for. : : : | ||||
| limit | integer | Optional: The | No | 50 |
| : : : maximum : : : | ||||
| : : : number of : : : | ||||
| : : : rows to : : : | ||||
| : : : return. : : : |
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/list_autovacuum_configurations.js 3.1 KB runs code
- scripts/list_available_extensions.js 3.1 KB runs code
- scripts/list_columnar_configurations.js 3.1 KB runs code
- scripts/list_columnar_recommended_columns.js 3.1 KB runs code
- scripts/list_installed_extensions.js 3.1 KB runs code
- scripts/list_memory_configurations.js 3.1 KB runs code
- scripts/list_pg_settings.js 3.1 KB runs code
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.
- 12d ago First seen · 90 lines · 38 tokens per session scan A 6995f7d3fa46
alloydb-omni-optimize is a skill published in the GitHub repository tmolavi/mcp-agent-skills-hub (8 stars, last pushed 16d ago), licensed MIT. It adds 38 tokens to every session and 558 once invoked, about $0.0002 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-31.
Other skills, from other repositories
sql-queries
Write correct, performant SQL across all major data warehouse dialects (Snowflake, BigQuery, Databricks, PostgreSQL, etc.). Use when writing queries, optimizing slow SQL, translating between dialects, or building complex analytical queries with CTEs, window functions, or aggregations.
postgres
Execute read-only SQL queries against multiple PostgreSQL databases. Use when: (1) querying PostgreSQL databases, (2) exploring database schemas/tables, (3) running SELECT queries for data analysis, (4) checking database contents. Supports multiple database connections with descriptions for intelligent auto-selection.…
database-patterns
DB schema design and query tuning: normalization, indexing, N+1, transactions, EXPLAIN. Triggers: schema, index, slow query, N+1, PostgreSQL, MySQL, EXPLAIN, deadlock, query plan.
database-migrations-sql-migrations
SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, SQL Server.
api-database-postgresql
Direct PostgreSQL access with node-postgres (pg) -- connection pools, parameterized queries, transactions, streaming, LISTEN/NOTIFY, error handling.
postgres
PostgreSQL mastery -- advanced features, replication, partitioning, tuning, connection pooling.