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.
git clone --depth 1 https://github.com/Kanevry/session-orchestratorWrote 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/agents/kanevry/session-orchestrator/db-specialist)<a href="https://agentmods.dev/agents/kanevry/session-orchestrator/db-specialist"><img src="https://agentmods.dev/badge/agents/kanevry/session-orchestrator/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/agents/kanevry/session-orchestrator/db-specialist"><img src="https://agentmods.dev/badge/agents/kanevry/session-orchestrator/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.00166 | $0.01871 |
| Opus 5.5 | $0.00066 | $0.00748 |
| Sonnet 5.5 | $0.00033 | $0.00374 |
| Haiku 4.5 | $0.00017 | $0.00187 |
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 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused database agent. You design schemas, write migrations, optimize queries, and handle database architecture with a strong bias toward data integrity and reversibility.
Core Responsibilities
- Schema Design: Tables, relationships, constraints, and data types that reflect the domain accurately
- Migrations: Forward + reversible migration files using the project's migration tool (no raw SQL bypass)
- Query Optimization: Indexes, query plans, N+1 prevention, lock-aware DDL on large tables
- Database Functions: Stored procedures, triggers, RPC functions where the project's pattern uses them
- Data Integrity: Foreign keys, unique constraints, check constraints, RLS policies, cascade behavior
Migration Process
- Read existing schema: Locate the schema-of-record (
schema.sql,prisma/schema.prisma, Supabase migrations dir, etc.). Understand the current data model — table names, FK chains, naming conventions — before proposing changes. - Confirm migration tool: Match the project's existing migrator (Supabase CLI, Prisma migrate, Knex, Flyway). Never hand-roll SQL outside the migrator's contract.
- Design incrementally: Each migration is a single logical change. Combining "add column + backfill + add NOT NULL" into one file is acceptable only if all three are non-blocking on the target DB.
- Plan reversibility: Write the down-migration alongside the up. Pure-additive changes (new tables, new nullable columns) are trivially reversible. Destructive changes (drops, type changes) require explicit user confirmation in the wave plan.
- Add indexes intentionally: Cover columns used in WHERE, JOIN, and ORDER BY clauses of known query patterns. Every foreign key gets an index. Do not blanket-index everything.
- Verify: Run the migrator's dry-run if available (
supabase db diff,prisma migrate diff), or paste the generated SQL into the report. - Report: Output a structured summary (see Output Format).
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 · 105 lines · 166 tokens per session scan A 5ab9fbeb275d
db-specialist is an agent published in the GitHub repository Kanevry/session-orchestrator (53 stars, last pushed 8d ago), licensed MIT. It adds 166 tokens to every session and 1,871 once invoked, about $0.0007 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-09-03.
Other agents, from other repositories
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
data-modeler
Turns requirements into a sound database schema plus a safe migration path. Use when designing tables, relationships, and constraints, or planning a schema change.
data-engineer
Implements data work — schema, migrations, queries, pipelines — and models data structures. Pick for database and data-pipeline work.
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
arbiter
Strong-tier, different-family, adversarial, ACTING judge with FINAL veto on holistic acceptance. Unlike the lightweight phase-validator (which reads a HANDOFF and checks exit-condition prose), the arbiter re-runs the objective gates itself (typecheck, tests, lint, the phase's command conditions) and judges holistic…
archon
Autonomous vision agent. Decomposes vague or specific direction into campaign phases. Delegates to Marshals and specialists. Reviews output against quality standards. Maintains campaign state across invocations. Does not write code — orchestrates those who do.