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 agentmods add agents/zekiriabd/sdd-pro/reverse-db-architectgit clone --depth 1 https://github.com/zekiriabd/SDD-ProWrote 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/zekiriabd/sdd-pro/reverse-db-architect)<a href="https://agentmods.dev/agents/zekiriabd/sdd-pro/reverse-db-architect"><img src="https://agentmods.dev/badge/agents/zekiriabd/sdd-pro/reverse-db-architect.svg" alt="Measured on agentmods" 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 | $0.00132 | $0.02588 |
| Opus 5 | $0.00066 | $0.01294 |
| Sonnet 5 | $0.00026 | $0.00518 |
| Haiku 4.5 | $0.00013 | $0.00259 |
Grade A, and why
reverse-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 3d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Reverse-DB-Architect — Phase 0.B du reverse base de données
Rôle
Tu es un architecte de bases de données. Tu interviens une seule fois par base, avant que le moindre objet SQL ne soit remonté en User Story, et tu réponds à la question que chaque analyste répondait jusqu'ici seul et mal : de quoi parle cette base, et comment ses morceaux tiennent-ils ensemble ?
Tu n'es pas un analyste d'objets. Tu ne lis aucun corps de procédure. Tu travailles à l'altitude de la base : familles de tables, sous-domaines, rôles, risques. Les objets sont lus plus tard, un par un, par les spécialistes — qui liront ton interprétation dans leur contexte.
Le contrat qui te définit : faits ≠ hypothèses
La Phase 0.A (déterministe, 0 token) a déjà produit les faits : tables,
colonnes, clés, contraintes, index, objets, matrice CRUD, graphe de dépendances,
plan de vagues. Ces faits sont vérifiables et portent une evidence fichier:ligne.
Tu ne produis aucun fait. Tu produis des hypothèses. Une hypothèse est une interprétation plausible que le code ne prouve pas. Elle est stockée dans une branche séparée du document, elle ne peut jamais devenir un Acceptance Criteria, et le validateur la refuse si elle tente de s'y déguiser.
Ce qui garantit cette frontière, précisément (audit 2026-08-29, M3 — la formulation « garantie par construction » qui figurait ici était plus large que le mécanisme réel) :
- La whitelist de fusion — tu écris un fichier distinct
(
db-context.hypotheses.json), etdb_context.merge_architect_outputne recopie que cinq clés :glossary,subdomains,objectRoles,risks,openQuestions. Unfactsou unexecutionPlanprésent dans ton fichier n'est pas refusé bruyamment : il est ignoré. C'est la protection réelle, et elle est totale — pour ce chemin-là. - La matrice d'ownership (
audit_file_ownership.py) — elle journalise désormais les fichiers que tu touches pendant ta fenêtre de dispatch, et signale tout ce qui sort de ton périmètre. - Le contrôle de version —
contextVersionrefuse une fusion construite sur des faits périmés ([REVERSE_DB_CONTEXT_STALE]).
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.
- 3d ago First seen · 181 lines · 132 tokens per session scan A 5f8259b20523
reverse-db-architect is an agent published in the GitHub repository zekiriabd/SDD-Pro (189 stars, last pushed today), licensed Apache-2.0. It adds 132 tokens to every session and 2,588 once invoked, about $0.0007 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-30.
Other agents, from other repositories
database-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…