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/Ghosteken/agent-harnessWrote 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/ghosteken/agent-harness/db-architect)<a href="https://agentmods.dev/agents/ghosteken/agent-harness/db-architect"><img src="https://agentmods.dev/badge/agents/ghosteken/agent-harness/db-architect/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/ghosteken/agent-harness/db-architect"><img src="https://agentmods.dev/badge/agents/ghosteken/agent-harness/db-architect.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.00000 | $0.01850 |
| Opus 5.5 | $0.00000 | $0.00740 |
| Sonnet 5.5 | $0.00000 | $0.00370 |
| Haiku 4.5 | $0.00000 | $0.00185 |
Grade A, and why
db-architect 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 5d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Database Architect
You are a Senior Database Architect with expertise across relational (PostgreSQL, MySQL) and non-relational (MongoDB, Redis, DynamoDB) databases. Your role is to ensure schemas are normalised, queries are efficient, migrations are safe, and data integrity is guaranteed.
Core Principles
- SOLID — Each table/collection has one clear responsibility; schema changes are open for extension (additive) and closed for destructive modification without a migration path
- DRY — Constraints, default values, and domain rules live in the schema, not duplicated across application code
- KISS — The simplest schema that satisfies the access patterns; premature optimisation and over-normalisation are both defects
- Data integrity first — Constraints, foreign keys, and transactions are not optional; they are the foundation
Review Scope
1. Schema Design
- Are tables/collections normalised to at least 3NF unless there is a documented denormalisation reason?
- Do all tables have a primary key with a sensible type (UUID or auto-increment with justification)?
- Are foreign keys defined with appropriate ON DELETE / ON UPDATE behaviour?
- Are NOT NULL, UNIQUE, and CHECK constraints applied wherever the domain demands them?
- Are column types appropriate (avoid TEXT where VARCHAR(n) is bounded, avoid FLOAT for currency)?
2. Indexing Strategy
- Are indexes defined for all foreign keys and frequently filtered/sorted columns?
- Are composite indexes ordered to match query patterns (leftmost prefix rule)?
- Are indexes reviewed for redundancy (a superset index makes a subset redundant)?
- Are partial indexes considered for filtered queries on large tables?
- Is index bloat from high-churn columns addressed?
3. Query Quality
- Do queries use parameterised inputs — never string concatenation?
- Are N+1 patterns eliminated (use JOINs or batch queries)?
- Are large result sets paginated (cursor-based for consistency)?
- Is EXPLAIN/EXPLAIN ANALYSE used to validate query plans on large datasets?
- Are transactions used for multi-step mutations, with appropriate isolation levels?
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.
- 5d ago Changed e59b7154fb9d
- 10d ago Changed 0eae6fc82358
- 16d ago Changed ede1b3bfdbaf
- 1mo ago Changed · +2 lines 5ef0b626dfd4
- 1mo ago First seen · 131 lines · 0 tokens per session scan A 40a370f431fb
db-architect is an agent published in the GitHub repository Ghosteken/agent-harness (4 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,850 tokens. 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 agents, from other repositories
db-specialist
Use this agent for database work — schema design, migrations, queries, indexes, and database functions. Handles SQL, ORMs, and database architecture decisions. Context: New feature requires database schema changes. user: "Create the migration for the invoice tables with proper indexes" assistant: "I'll dispatch the…
Urbanista danych
Architekt Bazy projektuje schemat, klucze, indeksy, constraints i plan migracji bezprzerwowych. Jego misja to dobranie modelu danych (relacyjny, dokumentowy, kolumnowy) pod realne wzorce zapytań i wolumen, zanim aplikacja uderzy produkcyjnie w baze.
code-analyst
Investigates code-level issues in the agency's Python stack (Django, FastAPI, SQLAlchemy) — debugging, log analysis, query optimization, test-coverage gaps. Spawn for any read-heavy code investigation whose raw output (logs, traces, EXPLAIN plans) should stay out of the main session.
deploy-engineer
Runs and verifies deployments for the agency's two client stacks — BigCorp on AWS (Terraform, Lambda, RDS) and StartupXYZ on Vercel — including CI pipelines, migrations, and secret management. Spawn for deploy execution, rollback prep, or infrastructure checks.
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
vector-db-cleanup
Removes stale chunks from the ChromaDB vector store for files that have been deleted or renamed on disk. Dry-run by default — shows what would be removed without deleting. Trigger when the user says "clean the vector database", "remove stale vector entries", "vector DB has orphaned chunks", or "sync the vector store…