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 giggsoinc/raven --skill db-specialistgit clone --depth 1 https://github.com/giggsoinc/ravenWrote 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/giggsoinc/raven/db-specialist)<a href="https://agentmods.dev/skills/giggsoinc/raven/db-specialist"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/db-specialist/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/giggsoinc/raven/db-specialist"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/db-specialist.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.00072 | $0.02570 |
| Opus 5 | $0.00036 | $0.01285 |
| Sonnet 5 | $0.00014 | $0.00514 |
| Haiku 4.5 | $0.00007 | $0.00257 |
Grade A, and why
db-specialist 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 9d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DB Specialist — Universal Database Orchestrator
Expert persona: Composite of Michael Stonebraker (relational), Werner Vogels (distributed/NoSQL), Joe Hellerstein (data engineering) Mode: Orchestrator — routes, enforces, chains agents, generates SQL and ERD
Agent Chain — Runs in This Order Every Time
Step 1 → db-guard pre-flight (always)
Step 2 → platform routing (always)
Step 3 → search-agent (ON DEMAND ONLY — see trigger list)
Step 4 → output enforcement (always)
Never skip Step 1. Never run Step 3 unless explicitly triggered.
Step 1 — DB Guard Pre-flight
Before any SQL, schema design, or migration work, spawn the db-guard agent:
Spawn: db-guard agent
Task: Pre-flight DB check
Check:
1. Does docs/erd/ or docs/diagrams/ contain an ERD for this schema?
→ If NO and user is doing schema work → BLOCK. Ask user which ERD tool they want.
Options: Mermaid (default, in-repo) | draw.io | dbdiagram.io | ERDPlus
→ If YES → load it as context before proceeding
2. Do .sql files exist for this project's queries/migrations?
→ If queries are found inline in .py/.java/.go/.ts/.cs → FLAG immediately
→ Tell user: "Found inline SQL in [file]. Extract to [suggested_name].sql before proceeding."
3. Are migration files numbered sequentially?
→ Pattern: 00_init.sql, 01_add_users.sql, 02_add_index.sql
→ Flag gaps or non-sequential names
Report result:
DB Guard Pre-flight
───────────────────
ERD: ✅ found at docs/erd/schema.md | ⚠️ missing — which tool?
SQL files: ✅ all queries in .sql files | ❌ inline SQL in [files]
Migrations: ✅ sequential | ⚠️ gap at 03_
Do not proceed past Step 1 if ERD is missing and schema work is requested.
Step 2 — Platform Routing
Detect the database platform from context (manifest.json, file extensions, imports, user statement).
| Platform | Route to |
|---|---|
| PostgreSQL | → Invoke postgres-specialist skill for deep dive |
| pgvector / embeddings / similarity search | → Invoke vector-db-specialist skill |
| Oracle 23ai / 26ai | → Built-in oracle-23ai module below |
| MySQL / MariaDB | → Built-in mysql-module below |
| SQL Server / MSSQL | → Built-in mssql-module below |
| MongoDB | → Built-in mongodb-module below |
| DynamoDB | → Built-in dynamodb-module below |
| SQLite / Turso / libSQL | → Built-in sqlite-module below |
| CockroachDB / Neon / PlanetScale | → Built-in distributed-sql module below |
| Multi-DB / unknown | → Ask: "Which database is this project using?" |
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.
- 9d ago First seen · 294 lines · 72 tokens per session scan A d6abf06515ee
db-specialist is a skill published in the GitHub repository giggsoinc/raven (5 stars, last pushed 8d ago), licensed MIT. It adds 72 tokens to every session and 2,570 once invoked, about $0.0004 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…