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 AlexK020908/infra-designer --skill databasegit clone --depth 1 https://github.com/AlexK020908/infra-designerWrote 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/alexk020908/infra-designer/database)<a href="https://agentmods.dev/skills/alexk020908/infra-designer/database"><img src="https://agentmods.dev/badge/skills/alexk020908/infra-designer/database.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.1 | $0.00000 | $0.00350 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
database 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 7d 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.
What it actually says
supabase.database (Supabase Postgres)
A managed Postgres with a public, pooled, TLS endpoint — plus auth, storage, and realtime if you want them. The serverless-friendly database that pairs with a Vercel frontend or any external/edge compute. Provisioned in the Supabase dashboard, not IaC.
When to use
- Simple apps / MVPs where a full AWS data tier is over-engineering: a Vercel app + Supabase is git-push deploy, nothing to patch, generous free tier.
- Any compute that lives outside a VPC (Vercel, edge functions) and so cannot reach
aws.rds.postgres(which is VPC-private by the security floor).
vs aws.rds.postgres
aws.rds.postgres— VPC-private, reached over a security group from AWS compute; full control, pay for the instance. Use when the whole stack is in AWS and the DB must be private.supabase.database— public pooled TLS endpoint, reachable from anywhere with the connection string; near-zero ops. Use for the lightweight stack.
Connection
- Pooled connection (port 6543) for serverless/Vercel (many short-lived connections); direct (5432) for long-lived servers and migrations.
- The app reads the connection string from a secret/env var (e.g.
DATABASE_URL).
Edges
- A frontend/compute node connects to it with a data edge (it reads/writes over the public TLS endpoint). No security-group wiring — it's not a VPC resource.
What ships with it
2 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.
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.
- 7d ago First seen · 27 lines · 0 tokens per session scan A ff1d30697ac9
database is a skill published in the GitHub repository AlexK020908/infra-designer (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 350 tokens. 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
yida-db-seq-fix
A tool for checking and correcting PostgreSQL sequences, which generate automatic numeric IDs for new rows. It is designed for Yida databases after automatic table creation or data migration.
azure-database-postgresql
Expert knowledge for Azure Database for PostgreSQL development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Flexible Server, replicas, PgBouncer, Query Store, Redis…
azure-horizondb
Expert knowledge for Azure Horizondb development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using azureai SQL/embeddings, pgvector tuning, Apache AGE graphs, hybrid…
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.
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…
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…