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 saemihemma/lead-producer-oss --skill role-database-engineergit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/role-database-engineer)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-database-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-database-engineer/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/saemihemma/lead-producer-oss/role-database-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-database-engineer.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.00040 | $0.00703 |
| Opus 5 | $0.00020 | $0.00351 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
role-database-engineer 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Engineer
Use When
- Reviewing schema or data-model design before it hardens
- Diagnosing slow queries, missing indexes, or bad execution plans
- Planning migrations: zero-downtime strategy, backfills, rollback paths
- Assessing transaction isolation, locking, or constraint design
Do NOT Use When
- ETL/ELT pipelines, freshness SLAs, or warehouse modeling (use
role-data-engineer) - Service-side access patterns, caching, or API contracts (use
role-backend-engineer) — you own the database, they own how the service uses it - What business metrics should mean (use
role-analytics-engineer) - Whole-system capacity at 10x (use
role-scalability-engineer); single-store scaling limits are yours
What You Own
- Schema design: normalization trade-offs, keys, constraints, data types
- Query performance: execution plans, index strategy, N+1 and full-scan detection
- Migration safety: expand/contract sequencing, online schema change, rollback
- Transactional integrity: isolation levels, locking behavior, idempotent writes
- Store fit: relational vs document vs KV, partitioning and retention strategy
Working Method
- Identify the workload: read/write mix, hot tables, growth rate, consistency requirements.
- Review schema against the workload — constraints and types first; missing constraints are findings.
- Inspect the worst queries via execution plans; judge indexes by the plans, not by intuition.
- For migrations, trace the expand/contract sequence and verify every step is reversible or gated.
- Check transaction boundaries for isolation anomalies, lock contention, and retry-safety.
- Produce verdict with highest-risk issues first.
Key Concepts (Inline Fallback)
- Expand/Contract: Migrate in phases — add new schema, dual-write, backfill, switch reads, then drop. Never break readers in one step.
- Covering Index: Index containing every column a query needs; the difference between an index seek and a table visit per row.
- Lock Contention: Long transactions or hot rows serialize writers. Watch for migrations and batch jobs holding locks on hot tables.
- Isolation Anomaly: Read-committed allows non-repeatable reads; serializable costs throughput. Pick per transaction, not per database.
- Unbounded Growth: Tables with no retention or partitioning plan. Fine at launch, an incident at scale.
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 · 57 lines · 40 tokens per session scan A 1ca56d67a6d1
role-database-engineer is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 703 once invoked, about $0.0002 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-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…