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 rds-postgresgit 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/rds-postgres)<a href="https://agentmods.dev/skills/alexk020908/infra-designer/rds-postgres"><img src="https://agentmods.dev/badge/skills/alexk020908/infra-designer/rds-postgres.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.00881 |
| Opus 5 | $0.00000 | $0.00441 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
rds-postgres 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 8d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aws.rds.postgres
Single-node managed Postgres. Default choice for relational data — and often replaces other nodes (see "Built-ins"). Config knobs: instanceClass, storageGB, encrypted, multiAz, publiclyAccessible, dbName.
Sizing & ceilings (single node, per core — scale with instanceClass)
- Simple inserts ~5k/s; updates touching indexes ~1-2k/s; complex multi-table transactions: hundreds/s; bulk loads: tens of thousands of rows/s.
- Simple indexed reads 50k+/s; indexed joins thousands-tens of thousands/s; analytical aggregations hundreds-low thousands/s.
- Writes are gated by WAL flush (disk I/O); every extra index adds WAL entries and cuts write throughput. Reads are bound by whether the working set fits in RAM — if it spills, performance drops sharply.
db.t4g.micro(default, ~$12/mo, 1 GiB RAM) fits prototypes/<10k users; bumpinstanceClassfor more RAM/cores before any architectural change. - Rules of thumb: tables get unwieldy past 100M rows; complex joins strain past 10M rows; full-text search fine to tens of millions of docs.
storageGB: 20default — size for data + indexes + WAL headroom. - Connections: each one is a forked OS process — hundreds of connections burn RAM and CPU on context switching. Connection pooling is mandatory: tell the coding agent to use PgBouncer/RDS Proxy or app-side pooling, sized small (especially with many app instances or Lambda).
Built-ins that remove other nodes (at modest scale)
- JSONB + GIN index: flexible/document data with
@>containment queries — often no DynamoDB/Mongo node needed. Schema choice itself: see data-modeling.md. - Full-text search:
tsvectorcolumn + GIN index,@@ to_tsquery(...)— stemming, ranking, AND/OR/NOT. Replaces OpenSearch until you need fuzzy/typeahead, facets, custom relevance, or distributed scale (escalation ladder: db-indexing.md). - LISTEN/NOTIFY: lightweight pub/sub for cache invalidation or change signals — no broker node for small fan-out (not durable; missed if listener is down).
SELECT ... FOR UPDATE SKIP LOCKED: a jobs table becomes a work queue — skips SQS at modest throughput; escalate to SQS when volume or retry semantics outgrow it.- PostGIS extension + GiST index: radius/containment geo queries without a specialized geo store.
What ships with it
3 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.
- 8d ago First seen · 31 lines · 0 tokens per session scan A ecc374a282b1
rds-postgres 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 881 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
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…
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…
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.
doris-debug-cloud
Use for Doris storage-compute separation (cloud mode) issues: meta-service latency, cache miss storms, object store throughput, and shared-nothing config conflicts in compute groups.
azure-cosmos-db
Expert knowledge for Azure Cosmos DB development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Cosmos DB SQL/Mongo/Cassandra APIs, change feed, vector search…
azure-sql-database
Expert knowledge for Azure SQL Database development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when planning DTU/vCore tiers, Hyperscale, geo-replication/DR, Data…