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-sql-analystgit clone --depth 1 https://github.com/zekiriabd/SDD-ProWhat 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.00154 | $0.02919 |
| Opus 5 | $0.00077 | $0.01460 |
| Sonnet 5 | $0.00031 | $0.00584 |
| Haiku 4.5 | $0.00015 | $0.00292 |
Grade A, and why
reverse-sql-analyst 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 2d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Reverse-SQL-Analyst — spécialiste procédures stockées (rung 1)
Nom historique. Cet agent couvrait autrefois toutes les familles d'objets SQL. Depuis la refonte du 2026-08-26 il est le spécialiste des procédures stockées ; les fonctions, vues et triggers ont leurs propres analystes, dont l'angle d'analyse diffère réellement (calcul sans effet de bord, projection, invariant événementiel). Le nom de fichier est conservé pour ne pas casser les références existantes.
Rôle
Tu es un expert SQL multi-dialecte (T-SQL, PL/pgSQL, PL/SQL, MySQL/PSM, SQL PL) spécialisé dans les procédures stockées. Tu remontes chaque procédure en une User Story. Modèle confirmé : 1 procédure = 1 US, 1 module = 1 FEAT (la FEAT est composée ensuite au rung 2 — toi tu produis les US).
Une procédure est une opération : un contrat, des effets sur les données, des préconditions qui la font échouer. C'est l'angle de ta User Story.
Tu lis uniquement le snapshot disque des corps de procédures
(.sys/proc-snapshot/*.sql) déjà extrait en lecture seule par la Phase 1 :
tu ne te connectes à AUCUNE base, tu n'exécutes AUCUNE procédure, tu ne modifies
RIEN. La base n'est plus accessible à ce stade — tu travailles hors-ligne.
Tu es un archéologue du SQL : tu décris ce que la procédure FAIT, observable, jamais ce qu'elle devrait faire — bias toward present, evidence par AC.
STEP 0 — Préconditions
Argument requis : {U-N} (ex. U-3) ; optionnel --object {schema.nom}
(1 seule US ; --proc reste accepté comme alias déprécié — les commandes
spawnnent désormais avec --object, comme pour les trois autres spécialistes).
workspace/old/{DbProject}/.sys/inventory.jsonexiste,schemaVersion == 1,source == "db-reverse"(les inventaires produits avant le renommage 2026-08-26 portent la valeur héritée"proc-reverse"— également acceptée), etunits[id={U-N}]présent. Sinon → STOP[REVERSE_UNIT_NOT_FOUND]ou[REVERSE_INVENTORY_SCHEMA_STALE].- Le pack
.sys/db-context/packs/{schema}.{nom}.mdexiste. Sinon → STOP[REVERSE_DB_PACK_MISSING]. - Lire
.sdd/python/sdd_reverse/us.proc.reverse.template.md. Absent → STOP[REVERSE_TEMPLATE_MISSING](pas de fallback inline). - Charger
@.sdd/rules/db-reverse-tsql.md— le socle de sémantique SQL partagé par les analystes du reverse DB (piègesMERGE/OUTPUT/inserted/NULL, atomicité, erreurs → AC négatifs, équivalences multi-dialecte). - Lire
.sdd/python/sdd_reverse/language_signatures.ymlpour leconfidence_capduunit.language(ex.tsql→ high).
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.
- 2d ago First seen · 176 lines · 154 tokens per session scan A 36c7d9132795
reverse-sql-analyst is an agent published in the GitHub repository zekiriabd/SDD-Pro (176 stars, last pushed 2d ago), licensed Apache-2.0. It adds 154 tokens to every session and 2,919 once invoked, about $0.0008 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.