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 soden46/engineer-flow --skill databasegit clone --depth 1 https://github.com/soden46/engineer-flowWrote 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/soden46/engineer-flow/database)<a href="https://agentmods.dev/skills/soden46/engineer-flow/database"><img src="https://agentmods.dev/badge/skills/soden46/engineer-flow/database/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/soden46/engineer-flow/database"><img src="https://agentmods.dev/badge/skills/soden46/engineer-flow/database.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.00024 | $0.00458 |
| Opus 5.5 | $0.00010 | $0.00183 |
| Sonnet 5.5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database
Use this skill for persistence, queries, schema changes, migrations, transactions, data integrity, and data-access behavior.
This skill is language, ORM, and database framework agnostic.
Data Integrity
Enforce important invariants at the strongest practical layer.
Use appropriate:
- constraints
- uniqueness rules
- foreign keys
- nullability
- validation
- transaction boundaries
Application validation does not replace database integrity where concurrent writes can violate an invariant.
Queries
Prefer structured and parameterized query mechanisms.
Avoid:
- unbounded reads
- unnecessary columns
- repeated identical queries
- N+1 access patterns
- avoidable full scans
- query construction from untrusted input
Inspect the actual workload before adding optimization complexity.
Transactions
Use transactions when multiple operations must succeed or fail as one logical change.
Keep transaction scopes as small as practical.
Consider:
- partial failure
- retries
- deadlocks
- external side effects
- long-running work
Do not hold database transactions open while performing unnecessary external operations.
Concurrency
When correctness depends on concurrent access, explicitly consider:
- lost updates
- duplicate creation
- stale reads
- locking
- atomic operations
- optimistic concurrency
- idempotency
Do not assume application-level checks remain valid between read and write.
Schema Changes
Schema changes should consider:
- backwards compatibility
- existing data
- nullability
- defaults
- index creation
- rollout ordering
- rollback strategy
- large table impact
For risky migrations, prefer staged changes.
Data Access Boundaries
Keep persistence concerns separate from unrelated presentation or transport logic.
Avoid leaking database-specific details throughout the application when an established data-access boundary exists.
Verification
Relevant checks may include:
- correct persisted state
- constraint enforcement
- transaction rollback
- concurrent behavior
- query count
- execution plan
- migration safety
- backwards compatibility
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 · 112 lines · 24 tokens per session scan A 593b4eea8d2c
database is a skill published in the GitHub repository soden46/engineer-flow (3 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 458 once invoked, about $0.0001 per session on Opus 5.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
database-expert
Advanced database design and administration for PostgreSQL, MongoDB, and Redis. Use when designing schemas, optimizing queries, managing database performance, or implementing data patterns.
generic-fullstack-feature-developer
Guide feature development for full-stack applications with architecture focus. Covers Next.js App Router patterns, NestJS backend services, database models, data workflows, and seamless integration. Use when adding new features, refactoring existing code, or planning major changes.
agent-database-expert
Specialist subagent: Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance.
azure-data-tables-java
Build table storage applications using the Azure Tables SDK for Java. Works with both Azure Table Storage and Cosmos DB Table API.
bullmq-specialist
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications.
azure-data-tables-py
Azure Tables SDK for Python (Storage and Cosmos DB). Use for NoSQL key-value storage, entity CRUD, and batch operations.