Borrowing it
Nothing to install: this file belongs to mtnyilmaz/agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mtnyilmaz/agents/main/.agents/skills/database-developer/SKILL.mdgit clone --depth 1 https://github.com/mtnyilmaz/agentsWrote 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/mtnyilmaz/agents/database-developer)<a href="https://agentmods.dev/skills/mtnyilmaz/agents/database-developer"><img src="https://agentmods.dev/badge/skills/mtnyilmaz/agents/database-developer/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/mtnyilmaz/agents/database-developer"><img src="https://agentmods.dev/badge/skills/mtnyilmaz/agents/database-developer.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.00046 | $0.00677 |
| Opus 5.5 | $0.00018 | $0.00271 |
| Sonnet 5.5 | $0.00009 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
database-developer 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Developer
Expert in database design, Prisma ORM, PostgreSQL, and Redis for this monorepo.
Layer References
Schema templates, naming rules, soft-delete, query patterns, and migrations are covered in
layers/project/typescript/database-patterns.md. This skill adds relation examples, Redis caching, and indexing advice not found in layers.
Enum Pattern
enum UserRole {
OWNER
SUPER_ADMIN
ADMIN
USER
}
model User {
role UserRole @default(USER)
}
Relation Patterns
// One-to-many
model User {
id String @id @default(cuid())
products Product[]
}
model Product {
userId String
user User @relation(fields: [userId], references: [id])
}
// Many-to-many (explicit join table for extra fields)
model UserOrganization {
userId String
organizationId String
role UserRole @default(USER)
joinedAt DateTime @default(now())
user User @relation(fields: [userId], references: [id])
organization Organization @relation(fields: [organizationId], references: [id])
@@id([userId, organizationId])
}
Redis Patterns
Cache with TTL
import { redis } from "./redis";
async function getCachedUser(id: string) {
const cached = await redis.get(`user:${id}`);
if (cached) return JSON.parse(cached);
const user = await db.user.findUnique({ where: { id } });
await redis.set(`user:${id}`, JSON.stringify(user), "EX", 300); // 5 min
return user;
}
Cache invalidation on mutation
async function updateUser(id: string, data: UpdateUserInput) {
const user = await db.user.update({ where: { id }, data });
await redis.del(`user:${id}`);
return user;
}
Indexing Strategy
- Index all foreign keys (
@@index([userId])) - Index frequently filtered columns (
@@index([email]),@@index([createdAt])) - Composite indexes for common query patterns (
@@index([organizationId, role])) - Unique constraints where needed (
@@unique([email])) - Every soft-delete model must have
@@index([userId, deletedAt])— without it,WHERE deletedAt IS NULLqueries degrade to full table scans as zombie rows accumulate
What ships with it
1 file 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.
- 1mo ago First seen · 100 lines · 46 tokens per session scan A af2538b7a34f
database-developer is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 677 once invoked, about $0.0002 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
haven-db
Reset, reseed, locate and prune a haven stack's databases with haven db, and know which verbs destroy data. Use when someone says 'haven db', 'reset the database', 'drop the database', 'reseed in place', 'db preset', 'demo preset', 'database url', 'connection string for postgres', 'haven db prune', 'haven seed'…
nw-database-technology-selection
Database comparison catalogs, RDBMS vs NoSQL selection criteria, CAP/ACID/BASE theory, OLTP vs OLAP, and technology-specific characteristics.
vercel-storage
Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
quarry
Query PostgreSQL, MySQL, Redis and Neptune with Quarry (qy), compare data across environments, maintain reusable queries, and manage connections or the database workbench. Use for database evidence or explicit Quarry tasks, not general database design discussions.
query
Query optimization and EXPLAIN analysis.
vercel-storage
Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.