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 preset-io/agent-skills --skill preset-database-connectionsgit clone --depth 1 https://github.com/preset-io/agent-skillsWrote 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/preset-io/agent-skills/preset-database-connections)<a href="https://agentmods.dev/skills/preset-io/agent-skills/preset-database-connections"><img src="https://agentmods.dev/badge/skills/preset-io/agent-skills/preset-database-connections/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/preset-io/agent-skills/preset-database-connections"><img src="https://agentmods.dev/badge/skills/preset-io/agent-skills/preset-database-connections.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.00050 | $0.00430 |
| Opus 5 | $0.00025 | $0.00215 |
| Sonnet 5 | $0.00010 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
preset-database-connections 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.
What it actually says
preset-database-connections
Use for credential-bearing database connection reads and database connection changes.
Always
- Auth and conventions come from
preset-api(JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known. - Prefer
preset-datasetsmetadata before reading connection configuration. - Treat connection configuration as credential-bearing even on
GET. - Get explicit confirmation before configuration reads, validation, OAuth, upload, create, update, or delete.
- Redact SQLAlchemy URIs, passwords, private keys, SSH tunnel passwords, server certificates, access tokens, and engine
extrasecrets.
Decision Rules
- Classify connection configuration as credential-bearing.
- Permit metadata summary only unless the user approves a credential-bearing read.
- Require approval before credential-bearing configuration reads, validation, OAuth, upload, create, update, sync permissions, or delete.
- Forbid printing URI, password, private key, token, certificate, SSH password, or engine extras.
Workflow Order
- Resolve database connection metadata.
- Identify credential-bearing fields and endpoint risk.
- Prepare approval summary for configuration read, validation, OAuth, upload, create, update, or delete.
- Stop before credential-bearing configuration read, validation, OAuth, upload, create, update, or delete.
Retrieve
- Connection configuration routing: references/connection-configuration.md
- Credential-bearing configuration reads and redaction: references/connection-credential-reads.md
- Validation, OAuth, upload, create/update/delete, sync permissions: references/connection-mutations-and-validation.md
- Approval policy: load
preset-apiand thenreferences/safety-policy.md.
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.
- 12d ago First seen · 38 lines · 50 tokens per session scan A 70284fefe13b
preset-database-connections is a skill published in the GitHub repository preset-io/agent-skills (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 430 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.
Other skills, from other repositories
business-intelligence-expert
Build comprehensive business intelligence solutions including data warehouses, ETL pipelines, interactive dashboards, and analytical reporting systems. Use when the user mentions BI, data warehousing, star or snowflake schemas, OLAP cubes, ETL/ELT pipelines, dashboards, KPIs, or analytical reporting.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
chroma
Embedding database for RAG and semantic search.
pinecone
Managed vector DB for production RAG and search.
postgres-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Quick reference for common patterns, index types, data types, and anti-pattern detection. Based on Supabase best practices.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.