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-postgres-admingit 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-postgres-admin)<a href="https://agentmods.dev/skills/tmolavi/mcp-agent-skills-hub/alloydb-postgres-admin"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/alloydb-postgres-admin/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-postgres-admin"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/alloydb-postgres-admin.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.00039 | $0.01464 |
| Opus 5.5 | $0.00016 | $0.00586 |
| Sonnet 5.5 | $0.00008 | $0.00293 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
alloydb-postgres-admin 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.
This is a copy
98% identical to alloydb-postgres-admin — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
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
create_cluster
Creates a new AlloyDB cluster. This is a long-running operation, but the API call returns quickly. This will return operation id to be used by get operations tool. Take all parameters from user in one go.
Parameters
| Name | Type | Description | Required | Default |
|---|---|---|---|---|
| project | string | The GCP project ID. This is pre-configured; do not ask for it unless the user explicitly provides a different one. | No | |
| location | string | The location to create the cluster in. The default value is us-central1. If quota is exhausted then use other regions. | No | us-central1 |
| cluster | string | A unique ID for the AlloyDB cluster. | Yes | |
| password | string | A secure password for the initial user. | Yes | |
| network | string | The name of the VPC network to connect the cluster to (e.g., 'default'). | No | default |
| user | string | The name for the initial superuser. Defaults to 'postgres' if not provided. | No |
create_instance
Creates a new AlloyDB instance (PRIMARY or READ_POOL) within a cluster. This is a long-running operation. This will return operation id to be used by get operations tool. Take all parameters from user in one go.
Parameters
| Name | Type | Description | Required | Default |
|---|---|---|---|---|
| project | string | The GCP project ID. This is pre-configured; do not ask for it unless the user explicitly provides a different one. | No | |
| location | string | The location of the cluster (e.g., 'us-central1'). | Yes | |
| cluster | string | The ID of the cluster to create the instance in. | Yes | |
| instance | string | A unique ID for the new AlloyDB instance. | Yes | |
| instanceType | string | The type of instance to create. Valid values are: PRIMARY and READ_POOL. Default is PRIMARY | No | PRIMARY |
| displayName | string | An optional, user-friendly name for the instance. | No | |
| nodeCount | integer | The number of nodes in the read pool. Required only if instanceType is READ_POOL. Default is 1. | No | 1 |
What ships with it
8 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/create_cluster.js 3.1 KB runs code
- scripts/create_instance.js 3.1 KB runs code
- scripts/database_overview.js 3.1 KB runs code
- scripts/get_cluster.js 3.1 KB runs code
- scripts/get_instance.js 3.1 KB runs code
- scripts/list_clusters.js 3.1 KB runs code
- scripts/list_instances.js 3.1 KB runs code
- scripts/wait_for_operation.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.
- 1mo ago First seen · 148 lines · 39 tokens per session scan A 77eb785c5a2d
alloydb-postgres-admin is a skill published in the GitHub repository tmolavi/mcp-agent-skills-hub (8 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,464 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to alloydb-postgres-admin, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
cloud-sql-basics
This file generates or explains Cloud SQL resources. Use this file when the user asks to create a Cloud SQL instance or database for MySQL, PostgreSQL, or SQL Server. Cloud SQL manages third-party MySQL, PostgreSQL, and SQL Server instances as resources in Cloud SQL. For example, when Cloud SQL creates an open-source…
backup-restore
PostgreSQL backup and restore with pgBackRest — full/incremental/WAL, PITR, K8s CronJob scheduling, and restore verification.
db-performance
PostgreSQL query performance — EXPLAIN ANALYZE, index design, pgstatstatements, slow query detection, connection pool tuning.
postgres-operations
PostgreSQL operational runbooks — health checks, vacuum, bloat, locks, PITR, connection pool management.
cockroachdb
Expert CockroachDB distributed SQL assistance covering global ACID transactions, Raft consensus, multi-region survivability, and geo-partitioning. Use when scaling relational PostgreSQL workloads across multiple clouds or regions.
cosmosdb
Expert Azure Cosmos DB assistance covering NoSQL API, partition key design, Request Units (RU/s) optimization, and change feed. Use when building globally distributed, multi-master Azure applications.